#asahi-dev · 2025-02-27 18:50
svenouch#asahi-dev · 2025-02-27 18:47
svenI'd need a M2 to actually figure out what's going in that series and there's other stuff I'd rather do first#asahi-dev · 2025-02-27 18:37
svenm1n1 is a different story, will gladly review and merge M3/M4 stuff (or anything else) there#asahi-dev · 2025-02-27 18:36
sveni'll happily review series sent upstream but other than that I also don't think we have the capacity right now to add even more downstream patches to our kernel :(#asahi-dev · 2025-02-27 18:34
svenfair#asahi-dev · 2025-02-27 18:31
svenchaos_princess: is there any PR that's been updated recently? last i looked there were a few that had unaddressed review comments#asahi-dev · 2025-02-27 18:11
sveni guess he meant T8132 which would be M4, see e.g. https://asahilinux.org/docs/Codenames/#socs#asahi-dev · 2025-02-27 12:30
sventhe rpi pico pads are fairly large fwiw#asahi-dev · 2025-02-27 12:18
sven"not found"#asahi-dev · 2025-02-27 12:16
svencan you paste the pmgr node of the firmware adt somewhere? #asahi-dev · 2025-02-27 12:11
svenhm... so it's truly missing even in the filled in adt then :/#asahi-dev · 2025-02-27 12:06
svenmight just be hard-coded in the pmgr kext then :/#asahi-dev · 2025-02-27 12:06
svenyeah, if it's still missing there it's gonna be annoying to track ps-regs down#asahi-dev · 2025-02-27 12:04
svenso i'd first take a look at a "real" one before concluding that ps-regs really is missing#asahi-dev · 2025-02-27 12:04
sventhat may have changed for some reason. all i can say is that the template adt generally misses stuff#asahi-dev · 2025-02-27 12:04
svenyou have to get a dump from a booted machine to get the "real" ADT#asahi-dev · 2025-02-27 12:03
sventhat's just the ADT template that gets filled in by iboot during early boot#asahi-dev · 2025-02-27 12:03
sventhat explains why you don't have any ps-regs#asahi-dev · 2025-02-27 12:00
svenok, how did you get that adt? dumped from a booted machine with m1n1?#asahi-dev · 2025-02-27 11:41
svennot inside the pmgr node but inside devices nodes to refer to ps-regs inside pmgr #asahi-dev · 2025-02-27 11:41
sveni mean clock-gates #asahi-dev · 2025-02-27 10:25
svendo adt devices nodes still have that clock-gates (?) property?#asahi-dev · 2025-02-26 20:44
svenyeah, but the biggest challenge still is gpu para virtualization #asahi-dev · 2025-02-23 16:22
svenno idea either, but my assumption would be that it's just sampling time the cpu is stuck in wfi or whatever#asahi-dev · 2025-02-23 16:18
svenbut sart2_set_entry makes no sense there#asahi-dev · 2025-02-23 16:18
svensounds like a bug in the GUI frontend tbh. never looked into cpuidle, but cpuidle_enter_state showing up might just mean that well, that cpu is idling a lot :D#asahi-dev · 2025-02-23 15:57
svenand then never touch sart again#asahi-dev · 2025-02-23 15:57
svenit should do that a few times when the device probes and is initialized#asahi-dev · 2025-02-23 15:56
svenno, that's weird#asahi-dev · 2025-02-23 10:45
svenI can eventually review those things myself as well but if you get a r-b or t-b by other people more familiar with pre-m1 stuff I can just merge these things immediately #asahi-dev · 2025-02-23 10:44
svennickchan: yeah, I think I was confused because I saw the driver a few times already #asahi-dev · 2025-02-22 17:16
svenhttps://lore.kernel.org/asahi/20250220-caches-v1-0-2c7011097768@gmail.com/ was supposed to be the second one#asahi-dev · 2025-02-22 17:09
svenoh, they are only two days old. i somehow thought there were already on the list a while longer#asahi-dev · 2025-02-22 17:09
svenit would also be helpful to reviewed-bys or tested-bys on https://lore.kernel.org/asahi/20250220-dwi-dt-v1-0-d742431c7373@gmail.com/ and https://lore.kernel.org/asahi/20250220-dwi-dt-v1-0-d742431c7373@gmail.com/ before I can merge them#asahi-dev · 2025-02-22 17:02
sveni'll let them sit on the ML for a week or two and wait for some reviews and then just pull them into asahi-soc/* for the next PR#asahi-dev · 2025-02-22 17:01
svenokay, send out those rtkit fixes#asahi-dev · 2025-02-22 16:51
svennot trying to stop you, just confused why we need all that complexity inside m1n1 :)#asahi-dev · 2025-02-22 16:49
svenjannau: ack, so that commit likely needs a do-over now that the renesas part is a proper module#asahi-dev · 2025-02-22 16:48
sven*on#asahi-dev · 2025-02-22 16:48
svenxart/gigalocker is continuous in the disk fwiw, so all we need to do is find its offset#asahi-dev · 2025-02-22 16:48
svenright, but why do we need that in m1n1?#asahi-dev · 2025-02-22 16:46
svenjannau: ok, so that xhci firmware handling needs looking at before we try to submit it#asahi-dev · 2025-02-22 16:37
svenalso, does anyone know why xhci-pci.c was renamed to xhci-pci-core.c in 150-xhci-firmware? #asahi-dev · 2025-02-22 16:36
svenok, so we can drop 1 or 2 and could submit the rest? wanna do that or should I take a look?#asahi-dev · 2025-02-22 16:33
svenjannau: is there anything preventing us from submitting those dcp-related rtkit fixes from 010-soc?#asahi-dev · 2025-02-22 16:28
svenhrm, why do we need no_std for apfs? do we need apfs for anything inside m1n1?#asahi-dev · 2025-02-09 12:37
svenhttps://github.com/AsahiLinux/linux/releases/tag/asahi-soc-dt-6.15 should be the signed tag then#asahi-dev · 2025-02-09 12:27
svenfeel free to ping jannau or me here on irc if we take that long to review or merge something again :)