#asahi-dev · 2025-05-12 16:03
FritzerMcQHi, I want to help you bringing Linux to Mac devices. I have read some of the documentation and various other subpages on the asahi website. Right now I only have a MacBook Air M3. Can I still help you with that? I have some rust experience and also some very basic re exp.#asahi-dev · 2025-05-12 15:21
kettenisbut that means we'd need to update the UEFI environment at some point (which hasn't happened for a while)#asahi-dev · 2025-05-12 15:18
kettenisu-boot doesn't depend on this and I can phase out the old compatibles in OpenBSD in a year or so#asahi-dev · 2025-05-12 15:16
kettenissounds like a bikeshed to me; we should try to push back against such changes#asahi-dev · 2025-05-12 15:12
kettenisguess I missed that review#asahi-dev · 2025-05-12 11:31
chadmedi might submit the core asoc changes after the 6.16 merge window too. that was annoying as shit to rebase#asahi-dev · 2025-05-12 11:29
chadmeduntested at the moment btw#asahi-dev · 2025-05-12 11:29
chadmedthe codec commits are pulled straight from the merged series and should automatically go away when rebased onto 6.16#asahi-dev · 2025-05-12 11:28
chadmedjannau: https://github.com/chadmed/linux/tree/for-janne#asahi-dev · 2025-05-12 05:22
sven*while#asahi-dev · 2025-05-12 05:22
svenyeah, that’s what I was thinking. just add it there and leave that code around for long whilen#asahi-dev · 2025-05-11 22:44
jannaum1n1 could append the old compatible if we don't get to fix it#asahi-dev · 2025-05-11 20:06
svenor sneakily adjust it in m1n1#asahi-dev · 2025-05-11 20:06
svenugh. maybe we can still fix that but we should at least ship a downstream device tree with the old compatible for quite a while #asahi-dev · 2025-05-11 18:33
mazfeels like a very late (or even too late) change, given how many systems have been deployed with this particular name.#asahi-dev · 2025-05-11 17:25
alyssahttps://lore.kernel.org/asahi/63957942-173e-4c28-932e-a8ba7c60ee83@gmail.com/#asahi-dev · 2025-05-11 17:24
alyssakettenis: upstream review feedback /shrug/#asahi-dev · 2025-05-11 10:42
svensmc errors from the kext#asahi-dev · 2025-05-11 10:42
svenhttps://gist.github.com/svenpeter42/c9467235de8e8f35471b686658fc77a3#asahi-dev · 2025-05-11 10:33
svenjannau: probably obvious, but macOS calls error 132 from smc kSMCKeyNotFound#asahi-dev · 2025-05-11 08:21
svenhttps://lore.kernel.org/asahi/20250511-smc-6-15-v5-0-f5980bdb18bd@svenpeter.dev/ smc v5#asahi-dev · 2025-05-10 22:39
floklity, I can confirm the noise is gone from the logs :-)#asahi-dev · 2025-05-10 16:49
jannauI've pushed asahi-6.14.6-1 to github. this get's rid of the annoying / confusing "property voltage_min not supported: -132" from macsmc ac power and supports systemd's RebootWatchdog default time out#asahi-dev · 2025-05-10 16:01
kettenis1why did the PMIC compatible have to change?#asahi-dev · 2025-05-10 15:36
jannauI stopped. I'll read over the v5 on github instead#asahi-dev · 2025-05-10 15:30
svenack, i'll wait for your review then. was planning to send out v5 tomorrow probably#asahi-dev · 2025-05-10 15:29
jannauyes, I did look. Same change I've done locally for the downstream tree#asahi-dev · 2025-05-10 15:28
svenmostly lee's and alyssa's comments addressed plus some drive-by fixes#asahi-dev · 2025-05-10 15:28
svenhttps://github.com/AsahiLinux/linux/commits/sven/smc-v5/ is what i have for v5 right now fwiw#asahi-dev · 2025-05-10 15:27
jannauack, just started writing a review for v4#asahi-dev · 2025-05-10 15:23
sven return -EIO;#asahi-dev · 2025-05-10 15:23
sven if (result)#asahi-dev · 2025-05-10 15:23
sven result = FIELD_GET(SMC_RESULT, smc->cmd_ret);#asahi-dev · 2025-05-10 15:22
svenI think i fixed that in v5#asahi-dev · 2025-05-10 15:19
jannauwe probably should not return 'FIELD_GET(SMC_RESULT, smc->cmd_ret);' negated and interpret it as errno. That ought to be the place the -132/ERFKILL is coming from#asahi-dev · 2025-05-10 15:12
nickchanit also only happens in gcc #asahi-dev · 2025-05-10 15:00
svenlol, yeah, I noticed those as well when I compiled smc with W=1 like lee requested earlier today :D#asahi-dev · 2025-05-10 14:59
nickchaneven though the original driver already has like 10 W=1 warnings already#asahi-dev · 2025-05-10 14:58
nickchani will send the pmu support series again i guess to fix that one W=1 compile warning that syzbot complained about#asahi-dev · 2025-05-10 14:57
nickchanand the deep sleep serror issues above is only a11 since a10 and below only has one cluster and obviously cpu0 is not in sleep#asahi-dev · 2025-05-10 14:56
sventhen i'm not gonna add that to that PR#asahi-dev · 2025-05-10 14:55
nickchansven: they were not cleared before#asahi-dev · 2025-05-10 14:55
svenhave we cleared the before?#asahi-dev · 2025-05-10 14:54
nickchansven: clear the wfi retention disable bit on startup on cores that supports arch retention and it should be good#asahi-dev · 2025-05-10 14:54
nickchansven: In any case at least the chickens PR does not have any *new* regressions on A7, A9, A10, A11#asahi-dev · 2025-05-10 14:40
nickchani will make sure it works for booting and secondary start i guess#asahi-dev · 2025-05-10 14:40
nickchanuntil i want to bother with idle in linux of course#asahi-dev · 2025-05-10 14:40
nickchanugh in any case i don't think i really care about what happens on that code path#asahi-dev · 2025-05-10 14:36
nickchana non deep sleep but i am quite sure that it was okay at one point