#asahi-dev · 2026-10-02 19:53
yukaI guess checking all of these on an M4 Pro macbook would be nice#asahi-dev · 2026-10-02 19:53
jannauyuka: msr1 appears to be the the scaler or at least related to it. possible that m4 pro has only one of those and m4 max has two#asahi-dev · 2026-10-02 19:36
yukaSomehow when I tested I was just like oh /dev/nvme0 shows up so it works#asahi-dev · 2026-10-02 19:36
yukaso like part of the separate nvmmu region which I had in v1 is needed after all#asahi-dev · 2026-10-02 19:36
yukaAw shit, I think the nvmmu things do not error but also do not do anything in the reg[9] region >_>#asahi-dev · 2026-10-02 19:25
jvoisinhuh, is there a reason for m1n1's license change?#asahi-dev · 2026-10-02 19:25
svenwould be nice to at least get that in#asahi-dev · 2026-10-02 19:25
sveni kinda hope i'll be able to finish at least the typec subsystem part and get that out tomorrow#asahi-dev · 2026-10-02 19:25
sventhere's probably still enough time if you send it out sometime next week for this cycle, but there's no rush. there's always the next one ;)#asahi-dev · 2026-10-02 19:22
yukaI also have a lot of nvme foo lined up after the basic device trees for M4 Pro/Max and M5, but currently it's somehow broken and only nvme0 turns up but not the namespaces (but maybe just broke my config file)#asahi-dev · 2026-10-02 19:21
sveni (or you) can send another smaller PR based on the first one #asahi-dev · 2026-10-02 19:21
sveni'm just going on vacation next week and figured i'd already send out whatever we have until now :D#asahi-dev · 2026-10-02 19:20
jannausven: did you omit the M3* nvme series because the the ans2 dt-bindings weren't picked up in nvme?#asahi-dev · 2026-10-02 19:03
jannauvenc1_sys is probably only present on M4 Max. at least apple's M4 Pro/Max press release mentions "M4 Max includes two video encode engines"#asahi-dev · 2026-10-02 19:03
kettenisjannau: while that is something the MIT license allows you to do it does mean you should not remove the MIT license#asahi-dev · 2026-10-02 19:00
svenyeah, my m4 pro only has three dcpext nodes#asahi-dev · 2026-10-02 19:00
jannauI think sven said the M4 Pro mini uses only dcpext* for its 3 supported displays. that would explain why disp_sys is absent on that device, compare m2 ultra which also only uses dcpext*#asahi-dev · 2026-10-02 18:58
yukadelete-node...#asahi-dev · 2026-10-02 18:58
yukaInteresting, I see something in t6032#asahi-dev · 2026-10-02 18:58
jannauthe isp ones are not useable on desktop devices. we disable (or enable) them based on whether the device has a camera#asahi-dev · 2026-10-02 18:57
sven*my#asahi-dev · 2026-10-02 18:57
svenif you give me a MMIO addreess i can try and trace them on me m4 pro tomorrow#asahi-dev · 2026-10-02 18:56
yukaps_isp_sys seems to be present in all of M1, M2, M3, M4 device trees#asahi-dev · 2026-10-02 18:55
yukaneither in M4 nor M4 Pro#asahi-dev · 2026-10-02 18:54
yukathey are not#asahi-dev · 2026-10-02 18:54
jannauyuka: aren't the *_SYS ones "no_ps: True"? in that case they are no powerstate power-domains and we have omitted them from the .dtsi. At least I did for M3*#asahi-dev · 2026-10-02 18:46
chaos_princessisn't this a problem on previous ones too, where some domains need the "externally-clocked" flag or sth#asahi-dev · 2026-10-02 18:45
yukait's the last blocker for sending the device trees kinda#asahi-dev · 2026-10-02 18:45
yukaany thoughts on what to do about the "Failed to reach power state 0xf" power domains on M4 pro?#asahi-dev · 2026-10-02 18:21
jannaukettenis: The relicense commit message isn't what I would have expected. The intention is to signal that future contributions will GPL2+ licensed. Combining MIT and GPL2+ licensed code is possible and the whole program is then GPL2+#asahi-dev · 2026-10-02 18:04
yukayou totally can#asahi-dev · 2026-10-02 17:59
kettenisI've not been asked#asahi-dev · 2026-10-02 17:59
kettenisyou can't change the license without agreement from *all* the copyright holders#asahi-dev · 2026-10-02 17:59
kettenisplease revert that license change#asahi-dev · 2026-10-02 13:09
noopwafelLarstiQ: the driver is still broken \o/ arrived home a few hours ago, very jetlagged today, pretty sure I know what's broken.. it really isn't _that_ huge a diff on the kernel side (esp. with initdata-in-m1n1). and the renderer is silly :D but the mesa/m1n1 drmshim is quite nice for bringup.#asahi-dev · 2026-10-02 13:01
myriaOkie, thanks!#asahi-dev · 2026-10-02 12:58
chaos_princessthe latter#asahi-dev · 2026-10-02 12:58
myriaThanks! Any reason for the license switch? Or should I wait for the 7.3 blog post?#asahi-dev · 2026-10-02 12:57
chaos_princessyes, the difference between 1.9.9 and 2.0.0 are only the license switch#asahi-dev · 2026-10-02 12:54
myriaAre there any more changes planned for v2.0.0 of m1n1? Or is that release just the relicense?#asahi-dev · 2026-10-02 12:21
barusuOkay, it's me again. I asked last time if I could help somewhere as a developer and I was told that Asahi project needed some extra hands on helping upstream some of the code. Is there anywhere I can specifically start or shadow?#asahi-dev · 2026-10-02 05:50
LarstiQnoopwafel: did you get the driver working half an hour after the talk? :) The renderer in m1n1 looks like fun#asahi-dev · 2026-10-01 20:59
devdragoupgraded target volume to 26 as sven suggested, bootloop is gone! still no connection via picocom-sec.sh on my host device, so i'll probably have to wait until i can do dcuart with another mac to confirm, but thank you all so much!#asahi-dev · 2026-10-01 20:01
yukaah disp_sys might make sense for hdmi#asahi-dev · 2026-10-01 20:00
yukawhy are they trying to reach 0xf anyways#asahi-dev · 2026-10-01 20:00
yukaI guess disp and isp don't make much sense on a Mac mini?#asahi-dev · 2026-10-01 19:59
yukadisp_sys isp_sys msr1 venc1_sys#asahi-dev · 2026-10-01 19:59
yukaor deduplicated#asahi-dev · 2026-10-01 19:58
yukavenc1_sys disp_sys msr1 isp_sys isp_sys venc1_sys disp_sys msr1 isp_sys isp_sys venc1_sys disp_sys msr1 isp_sys isp_sys venc1_sys disp_sys msr1 isp_sys isp_sys venc1_sys