#asahi-dev · 2026-10-03 11:07
chadmedthere are worse problems to have #asahi-dev · 2026-10-03 11:04
yukahorrible...#asahi-dev · 2026-10-03 11:04
myriaAlso, I understand the accumulation of apple devices now... I'm getting my third macbook soon (maybe)#asahi-dev · 2026-10-03 11:00
myriaAhhhh, Okie#asahi-dev · 2026-10-03 11:00
yukaI'm making a minimal diff now to bisect#asahi-dev · 2026-10-03 11:00
yukabut applying them to linux-next results in a non-working setup, while applying to v7.3-rc5 works#asahi-dev · 2026-10-03 11:00
yukayes#asahi-dev · 2026-10-03 11:00
myriayuka: are those changes in linux-next now? Last I checked they were only in a downstream tree#asahi-dev · 2026-10-03 10:58
yukaindeed#asahi-dev · 2026-10-03 10:56
yukaso maybe not a problem in the t8132-ans2 code after all#asahi-dev · 2026-10-03 10:55
yukaoh, fun, the new nvme failure mode (nvme0 appears, but no namespaces show up) only happens on linux-next 🫠#asahi-dev · 2026-10-03 10:54
chadmedthe core api already marks the owner of any locked kctls so idk why we were duplicating this in the first place#asahi-dev · 2026-10-03 10:54
chadmedim just going to get rid of the kctl ownership tracking stuff and be done with it#asahi-dev · 2026-10-03 09:57
sofusbut there are still the same suspicious writes#asahi-dev · 2026-10-03 09:56
sofushmm, on my m3 it has not rebooted yet, i waited ~9min#asahi-dev · 2026-10-03 09:30
sven5 seconds or so after the cores exited the hv it would reboot #asahi-dev · 2026-10-03 09:30
svenyes#asahi-dev · 2026-10-03 09:21
sofuswhen you tried getting macos to suspend?#asahi-dev · 2026-10-03 09:11
svenhuh, when I tried on my m1 it was much quicker #asahi-dev · 2026-10-03 08:58
sofusp.write32(u.adt["arm-io/pmgr"].get_reg(38)[0] + 0x4000, 1)#asahi-dev · 2026-10-03 08:58
sofusno ~50 seconds#asahi-dev · 2026-10-03 08:57
svenwhich also means the suspend somehow failed #asahi-dev · 2026-10-03 08:56
svenwhen I looked into it and failed I noticed it always rebooted after 5 or so seconds #asahi-dev · 2026-10-03 08:56
svenmight even be the normal one #asahi-dev · 2026-10-03 08:56
svenyeah, there’s some watchdog somewhere #asahi-dev · 2026-10-03 08:23
sofusi wonder what cancels that#asahi-dev · 2026-10-03 08:19
sofusmasking that should at least be usefull for figuring out resume stuff right?#asahi-dev · 2026-10-03 08:19
sofusit seems macos starts some kinda reboot timer right before suspending. Its just a random pmgr write, writing 0 does not cancel it#asahi-dev · 2026-10-03 07:11
svenofc you are in the history for those files, just use git log --follow#asahi-dev · 2026-10-03 04:05
nickchanin any case I am sure many people would like an explaination for changing the license#asahi-dev · 2026-10-03 04:03
nickchanby me#asahi-dev · 2026-10-03 04:03
nickchanmaybe it is clear which code is mit now but sometimes files will be renamed for exampel I am not in the history of src/chickens/hurricane_zephyr.c src/chickens/cyclone_typhoon.c src/chickens/twister.c src/chickens/monsoon_mistral.c despite being entirely authored by now#asahi-dev · 2026-10-03 03:57
chadmedwe will not be undoing the licence change for new code however just to be very clear. new code will not be dual-licenced.#asahi-dev · 2026-10-03 03:54
MichaelReeves[m]ok perfect thanks for explaining! :)#asahi-dev · 2026-10-03 03:53
chadmedand no you do not need to get rid of the fuchsia thing. our intention is _not_ to revoke MIT for existing code. it is silly to presume that we would do that#asahi-dev · 2026-10-03 03:53
nickchanyou could use the terms of commit 809541515659bf4e504807fd72bc0a539be5eee7#asahi-dev · 2026-10-03 03:53
chadmedwe are going to put the licence text back yes but no the spdx licence identifier does not need to specify dual licence. it is obvious which code was checked in under mit and which will not be#asahi-dev · 2026-10-03 03:53
nickchanlicenses cannot be revoked#asahi-dev · 2026-10-03 03:53
MichaelReeves[m]oh btw with the MIT licence change do I have delete t8122 fuchsia (it was just a quick throwaway project, so I don't really mind if so)? cause I looked at m1n1 AIC3 code but GPL and fuchsia licence aren't compatible (MIT is)#asahi-dev · 2026-10-03 03:51
nickchanjannau: please do not remove the MIT license, and all existing files probably need MIT AND GPL-2.0-or-later specified#asahi-dev · 2026-10-03 00:55
chadmedyessss lets go#asahi-dev · 2026-10-03 00:34
chadmedmaybe i can just refactor the called function so that it only acquires the semaphore when called from the workqueue #asahi-dev · 2026-10-03 00:34
chadmedhmm it seems to be deadlocking when called from slk_put/get#asahi-dev · 2026-10-03 00:04
chadmedso even nonblocking causes deadlocks if i take the rw semaphore from the volume limit workqueues...#asahi-dev · 2026-10-03 00:04
chadmedfrom the alsa crate docs: "Open does not support async mode (it’s not very Rustic anyway)"#asahi-dev · 2026-10-02 23:45
devdragoanyone know where i might be able to find more info on debugusb? Is it supposed to be a non-serial alternative to serial mode in macvdmtool? I seem to be able to create a connection to m1n1 via debugusb but not via serial#asahi-dev · 2026-10-02 22:08
yukaI ran into that but didn't find a full fix#asahi-dev · 2026-10-02 21:54
jannauhas anyone looked at macOS 15.x (or later) IPSWs for the installer? bootcaches.plist doesn't have bless2.RestoreBundlePath anymore#asahi-dev · 2026-10-02 21:20
jannaufixing SPMI usb in uefi-only: https://github.com/AsahiLinux/asahi-installer-data/pull/21#asahi-dev · 2026-10-02 20:01
jannauyuka: looking at the j773s/j614s/j614c template adt MSR1 is parent of MSR1_DART and the latter is clock/power-gate of dart-scaler1 but both m4 pro and max have scaler0 and scaler1