#asahi-dev · 2026-03-22 17:24
chaos_princessno rush ofc, just when time permits as this is something i can't confirm myself#asahi-dev · 2026-03-22 17:23
jannauI haven't tested yet#asahi-dev · 2026-03-22 17:20
chaos_princesswould also appreciate a confirm/deny that the new afnc and table implementations work#asahi-dev · 2026-03-22 17:19
chaos_princessyes, please#asahi-dev · 2026-03-22 17:19
jannauchaos_princess: do you want me to pull in my change to make DCAP optional?#asahi-dev · 2026-03-22 15:23
chaos_princessyea, it was a good time back then, but we lost a lot of time due to misreading the M as measurement :P#asahi-dev · 2026-03-22 15:22
chaos_princessah#asahi-dev · 2026-03-22 15:22
jannauchaos_princess: sorry, it was "might be a good time", fast forward 3-4 years, PMP driver #asahi-dev · 2026-03-22 15:16
chaos_princessjannau: i don't think i follow the implication. is it that it was being kept on so it does not write to pmp sram and crash as that was not powered?#asahi-dev · 2026-03-22 15:15
jannaufor usb keyboards it's probably more involved but suspend is currently in a sad state for the native type-c ports#asahi-dev · 2026-03-22 15:15
terrthank you!#asahi-dev · 2026-03-22 15:14
terrinteresting, okay, that was my read as well. i'll take a closer look#asahi-dev · 2026-03-22 15:13
jannauchaos_princess: "might be a good time to write a PMP driver" https://oftc.catirclogs.org/asahi-dev/2022-03-06#30702988#asahi-dev · 2026-03-22 15:11
jannauterr: afaik nobody has looked at it. if your lucky you just need to mark the right devices as wakeup source. I'd hope not that complicated for laptops keyboards#asahi-dev · 2026-03-22 14:53
terrHey folks, wondering what the status is for keyboard wakes? Is that actively being worked on, and/or is there appetite for someone picking that work up?#asahi-dev · 2026-03-22 14:29
jannaucould be related to macos not being able to wake dcp on m2 desktop devices after m1n1 used it#asahi-dev · 2026-03-22 14:25
jannauI can't remember what happens in macos#asahi-dev · 2026-03-22 14:25
chaos_princesskind of a problem for what i am doing since macos very much does turn off at least dcpexts via pmp#asahi-dev · 2026-03-22 14:23
jannauI suspect it might be crashing. rtkit doesn't comes up at all without min-state#asahi-dev · 2026-03-22 14:07
chaos_princesswhat was the reason for not fully powering down dcps when going to sleep? some missing initialization that they are losing?#asahi-dev · 2026-03-22 10:56
kaazooOK, thanks#asahi-dev · 2026-03-22 10:54
yukait does#asahi-dev · 2026-03-22 10:54
kaazooHi, does tag asahi-6.19.9-2 work with m1n1 1.5.2 ? I'm about to package a 6.19 kernel for Ubuntu Asahi.#asahi-dev · 2026-03-22 10:11
jannauI've tagged asahi-6.19.9-2, please use this instead of asahi-6.19.9-1#asahi-dev · 2026-03-22 09:39
chaos_princessno need#asahi-dev · 2026-03-22 09:37
jannauit was 6.19.7 based asahi-wip, I can push it somewhere#asahi-dev · 2026-03-22 09:35
chaos_princessbtw, when you tested on m1max with val |= 0x60000000 hack, what kernel version was it?#asahi-dev · 2026-03-22 09:33
jannaubut I wonder if it wouldn't make more sense if the power-domains notified pmp#asahi-dev · 2026-03-22 09:32
jannauI will remove the use of the pmp_report power-domains for now and tag another 6.19.9 kernel. In the worst case we will have at least one release with pmp-report support when the device tree starts using them#asahi-dev · 2026-03-22 09:29
jannauchaos_princess: no. integrated displays are always driven by dcp. on m1 and m1 pro/max/ultra the hdmi port is always driven by dcp#asahi-dev · 2026-03-22 09:10
chaos_princessare we using one of the dcpexts to drive the internal display on m1pro/max ?\#asahi-dev · 2026-03-21 21:33
chaos_princessuse macos 14.8.3 as base#asahi-dev · 2026-03-21 21:33
chaos_princesshttps://asahilinux.org/docs/sw/m1n1-user-guide/#asahi-dev · 2026-03-21 21:32
janekt2000[m]no not yet thats one of the things i know i need to learn.#asahi-dev · 2026-03-21 21:30
chaos_princessyou do know how to install m1n1 manually, right?#asahi-dev · 2026-03-21 21:29
janekt2000[m]ok thanks#asahi-dev · 2026-03-21 21:28
chaos_princessthose are pretty similar, so use m1pro/max or m2pro/max as reference#asahi-dev · 2026-03-21 21:28
chaos_princessand your specific board#asahi-dev · 2026-03-21 21:28
chaos_princessactually, you will have to adapt it to m3pro first#asahi-dev · 2026-03-21 21:27
chaos_princesscherry-pick that on top of asahi-wip#asahi-dev · 2026-03-21 21:27
janekt2000[m]so from where do i need to compile the kernel?#asahi-dev · 2026-03-21 21:24
chaos_princesshttps://github.com/AsahiLinux/linux/pull/446 - device trees from here#asahi-dev · 2026-03-21 21:24
chaos_princessoh, you only added the bindings there, right#asahi-dev · 2026-03-21 21:23
jannauthat won't work, no m3 pro / t603x devicetrees in asahi-wip#asahi-dev · 2026-03-21 21:22
chaos_princesscompile the latest m1n1, the kernel from asahi-wip and try#asahi-dev · 2026-03-21 21:21
janekt2000[m]Hello i have a MacBook Pro M3 Pro i would like to try and contribute to asahi. Is it currently possible to try and install it on this device or is it currently not possible? I am aware that there is no official installer.#asahi-dev · 2026-03-21 20:43
jannauyes, booting a 6.18 kernel with the 6.19 device tree#asahi-dev · 2026-03-21 20:39
yukaor else I don't understand how the new 6.19 tag could have any impact on 6.18 kernels#asahi-dev · 2026-03-21 20:39
yukado you mean in case a 6.18 kernel gets booted with a new 6.19 device tree?#asahi-dev · 2026-03-21 20:29
jannaucan't really think a good alternative though