#asahi-dev · 2025-10-07 11:50
chadmedill give it a couple of days though #asahi-dev · 2025-10-07 11:50
chadmedill add them both back for v4 then :P #asahi-dev · 2025-10-07 11:49
sveniirc usually that happens through MODULE_DEVICE_TABLE and some script/tool that picks those up and generates the required alias automatically (of in that case iirc)#asahi-dev · 2025-10-07 11:48
sveni think it needs that platform: prefix to be picked up#asahi-dev · 2025-10-07 11:41
chadmedmfd will register the platform device but will that alone trigger the module to load and probe? #asahi-dev · 2025-10-07 11:38
chadmedtheres so little documentation on mfd that searching for it yields results for memfd in the uapi docs#asahi-dev · 2025-10-07 11:33
sveni thought i found some code/documentation when i added it for macsmc-input but i can't find it again right now#asahi-dev · 2025-10-07 11:32
chadmedyeah ill have to add it back for macsmc-input wont i#asahi-dev · 2025-10-07 11:32
jannauI thought so as well and I only asked them to be removed for the misguided MFD_CELL_OF conversion#asahi-dev · 2025-10-07 11:31
chadmedi think the idea is that the mfd core takes care of it#asahi-dev · 2025-10-07 11:29
sventhough i never tried without it#asahi-dev · 2025-10-07 11:29
svenhm.. i thought the platform: alias was specifically there to make module autoloading work#asahi-dev · 2025-10-07 11:27
chadmedoh yeah lol we're due an rc soon#asahi-dev · 2025-10-07 11:26
jannau6.19. far too late for 6.18#asahi-dev · 2025-10-07 11:25
chadmedhopefully we can get this in and done for 6.18 #asahi-dev · 2025-10-07 11:25
chadmedv3 of the smc series sent#asahi-dev · 2025-10-07 09:27
chadmedill add it#asahi-dev · 2025-10-07 09:26
chadmedoh they were merged after the smc series#asahi-dev · 2025-10-07 09:23
chadmeddid we forget to add the smc rtc node to the t602x devicetrees?#asahi-dev · 2025-10-05 14:40
fl0_id(this is still with just usb, still need proper pinheaders for the central scrutinizer, so that it doesn't look too messy#asahi-dev · 2025-10-05 14:35
fl0_idas you guys just discussed m4 - tried booting linux kernel on the m3 recently ... unfortunately restarted, but I guess my custom dtb just has some bad adresses or sth.#asahi-dev · 2025-10-05 14:34
jannauI guess we don't really care that much for adt.py as that's just used for parsing/printing#asahi-dev · 2025-10-05 14:28
jannauwe can't rely on the size either since dart-aop.dapf-instance-0 has a length of 728 which is 13 * 56 == 14 * 52#asahi-dev · 2025-10-05 14:27
jannauthe adt is even inconsistent over macos versions. m3's dart-pmp.dapf-instance-0 is 1344 (24 * sizeof(DAPFT8110B)) in 15.1 vs. 1248 (24 * sizeof(DAPFT8110)) in 26.0#asahi-dev · 2025-10-05 14:23
jannau0x40 in dart-options unfortunately does not determine the dapf-instance layout#asahi-dev · 2025-10-05 13:45
svenlooks like eedaf2941a0 introduced the second call#asahi-dev · 2025-10-05 13:44
jannauwhy does m1n1/setup.py call .reset_panic_counter() twice? ended up duplicated due to a merge conflict?#asahi-dev · 2025-10-05 13:42
jannauI have them since ages, I was waiting on getting your refactoring in and when forgot#asahi-dev · 2025-10-05 13:36
svenoh, right, the base m3 chickens are still missing. we only have the pro/max ones#asahi-dev · 2025-10-05 13:29
jannauonly difference to the m4 version (except for the SoC) is that it still uses cd321x (the i2c usb type-c port controller)#asahi-dev · 2025-10-05 13:23
jannauI guess I should take this opportunity to submit the t8122 chickens and other m1n1 hw support#asahi-dev · 2025-10-05 13:22
jannauno reboots on the m3 macbook pro on tahoe (>4 minutes and counting)#asahi-dev · 2025-10-05 12:18
svennerd snipe successful :> #asahi-dev · 2025-10-05 12:18
jannauinstalls tahoe on the m3 macbook pro#asahi-dev · 2025-10-05 12:14
svenunless we really hit it with macos 26 fw as well#asahi-dev · 2025-10-05 12:13
svenyeah, that's why i'm not really convinced it's that#asahi-dev · 2025-10-05 12:13
jannaubut which co-proc would that be which isn't present or differently configured on the m4 mac mini#asahi-dev · 2025-10-05 12:12
svenmaybe it expects some co-processor to be booted ~early these days? but we should probably also hit that with macos 26 firmware on m1/m2 then i think#asahi-dev · 2025-10-05 12:11
sventhat sounds very strange#asahi-dev · 2025-10-05 08:44
jannauoh, that's unexpected. then it's definitively not wdt#asahi-dev · 2025-10-05 08:40
auscyber_i can leave it unattended and itll just restart forever#asahi-dev · 2025-10-05 08:39
auscyber_because its not a panic when it restarts#asahi-dev · 2025-10-05 08:37
auscyber_unless i force a panic by reading bad memory multiple times#asahi-dev · 2025-10-05 08:37
auscyber_it never brings up recovery when it reboots#asahi-dev · 2025-10-05 08:37
auscyber_i dont get recovery#asahi-dev · 2025-10-05 08:36
auscyber_yeah ill try that with serial#asahi-dev · 2025-10-05 08:33
jannauand possibly get reset_panic_counter.py working to avoid going through recovery every X reboots#asahi-dev · 2025-10-05 08:33
jannaucoprocessors like smc, pmgr, aop, sep, ... might have their own watchdog and/or can trigger resets on their own. I still think the best way forward is to look at the fault-info bits of the spmi pmu#asahi-dev · 2025-10-05 08:23
auscyber_like smc#asahi-dev · 2025-10-05 08:23
auscyber_wasnt our assumption that it was something else triggering watchdog unconditionally