#
#asahi-dev · 2025-04-15 16:37
nickchanmore specifically, overwrite the rest of the time stored in the pmic nvmem
#asahi-dev · 2025-04-15 16:36
nickchanit's doing that because the 194 days counter cannot be reset and time becoming wrong just because iOS is not running when that counter overflow is not great
#asahi-dev · 2025-04-15 16:35
nickchancan even reproduce by just setting the time in an iOS ramdisk
#asahi-dev · 2025-04-15 16:35
nickchanand the reason i have not implemented that rtc just yet that iOS *will* overwrite the time every boot
#asahi-dev · 2025-04-15 16:34
nickchanyou should keep it
#asahi-dev · 2025-04-15 16:33
chaos_princess?
#asahi-dev · 2025-04-15 16:33
chaos_princessso i should keep the mfd then
#asahi-dev · 2025-04-15 16:32
nickchan194 days of time
#asahi-dev · 2025-04-15 16:32
nickchana rtc that can count 194 of time and then a 32-bit value in the pmic nvmem to store the rest of the time
#asahi-dev · 2025-04-15 16:30
nickchanchaos_princess: I have verified the existence of an rtc in a11's spmi dialog da2422 pmic and is able to read time from it
#asahi-dev · 2025-04-15 16:27
chaos_princessi am asking since i am considering dropping it
#asahi-dev · 2025-04-15 16:27
chaos_princesslike?
#asahi-dev · 2025-04-15 16:27
nickchanchaos_princess: I could reuse it for other purposes I suppose
#asahi-dev · 2025-04-15 16:18
chaos_princessAny specific reason to keep simple-mfd-spmi driver around? It only ever gets used together with spmi-mfd-nvmem, and i do not see that much value in delineating specific nvmem ranges
#asahi-dev · 2025-04-15 16:09
svenbut it still works fine for my very outdated stage1 m1n1
#asahi-dev · 2025-04-15 16:09
sveni first thought i broke something with https://github.com/AsahiLinux/m1n1/pull/460 but this happens with the current m1n1 main for me
#asahi-dev · 2025-04-15 16:07
svenbut when i shared my m1n1.bin with jannau it also crashed for him
#asahi-dev · 2025-04-15 16:07
svencouldn't bisect it to a specific commit and no one else seems to have run into that
#asahi-dev · 2025-04-15 16:07
svensee logs from a few days ago, _something_ corrupts LR I think in the smp_call4 -> [other core] -> smp_secondary_entry -> mmu_secondary_setup path
#asahi-dev · 2025-04-15 16:05
nickchansven: what weird bug?
#asahi-dev · 2025-04-15 15:50
svenhttps://lore.kernel.org/asahi/20250415-pasemi-fixes-v2-0-c543bf53151a@svenpeter.dev/ pasemi fixes v2, time to get back to smc now (or get nerd sniped by that weird m1n1 bug again...)
#asahi-dev · 2025-04-15 15:46
nickchannevermind
#asahi-dev · 2025-04-15 09:15
nickchanm1n1 has a 4k paging code path too though it's not used on m4
#asahi-dev · 2025-04-15 09:15
nickchansome people say it may be broken
#asahi-dev · 2025-04-15 09:15
nickchanhave anyone tried 4k paging in el2 on m4?
#asahi-dev · 2025-04-14 12:42
alyssamaz: sounds good thanks
#asahi-dev · 2025-04-14 11:42
chadmedokay so the pcm does show up
#asahi-dev · 2025-04-14 11:07
chadmedid expect at least an alsa core error to be printed
#asahi-dev · 2025-04-14 11:02
jannauI think that would cause more obvious problems
#asahi-dev · 2025-04-14 10:48
chadmedthe alsa driver does get probed but i wonder if it's just the pcm that is not being created
#asahi-dev · 2025-04-14 10:45
jannaume neither. I suspect aop's audio endpoint works slightly different which triggers the strange error mode with aop_audio. I don't think I can do anymore tracing on t602x devices without mics
#asahi-dev · 2025-04-14 10:39
chadmedhard to troubleshoot without having the thing in front of me too :p
#asahi-dev · 2025-04-14 10:38
chadmedall reports of failure have been exactly the same - aop probes, pipewire can see the card as a node in the graph, but no useable source is created (not visible in pavucontrol or anywhere outside pw-cli) and the ucm profile is not applied
#asahi-dev · 2025-04-14 10:37
chadmedi cannot for the life of me figure out what is going on with j414 mics
#asahi-dev · 2025-04-13 20:24
svennope, just crashed when trying to start cpu 1
#asahi-dev · 2025-04-13 20:23
svenlet me try a few time
#asahi-dev · 2025-04-13 20:23
sveni think so, but i didn't pay close attention
#asahi-dev · 2025-04-13 20:22
jannaulooks that way. does always break at starting cpu 2?
#asahi-dev · 2025-04-13 20:17
svenso something somehow seems to corrupt lr there
#asahi-dev · 2025-04-13 20:17
svenit seems to break when returning from mmu_secondary_setup to smp_secondary_entry
#asahi-dev · 2025-04-13 20:15
jannauthat reproduces
#asahi-dev · 2025-04-13 20:09
svenhttps://f.svpe.dev/m1n1.bin that's the host one that almost always crashes when running run_guest.py for me
#asahi-dev · 2025-04-13 20:05
svenoh, duh, this won't crash for you: the issue is somewhere in the host m1n1
#asahi-dev · 2025-04-13 20:05
jannaudoes the execption happens before trying to mount the rootfs? it boots until that here
#asahi-dev · 2025-04-13 20:01
svenit's a raw binary, i switched to that to rule out macho issues
#asahi-dev · 2025-04-13 20:00
jannauthe binary fails for on macho parsing: https://paste.debian.net/1369328/
#asahi-dev · 2025-04-13 19:54
sventhe m1n1 has one patch that might annoying for you, i've hardcoded the serial_str to dummy_serial_str because my m1n1 bootobject still has that old code
#asahi-dev · 2025-04-13 19:54
svensee /msg
#asahi-dev · 2025-04-13 19:47
jannaucan you upload the m1n1+payload?
#asahi-dev · 2025-04-13 19:44
sventhe last few times it does the weird jump somewhere in mmu_secondary_setup but before reaching smp_secondary_entry again

plus ›