#
#asahi-dev · 2026-09-08 09:55
chadmedyes, that is wrong
#asahi-dev · 2026-09-08 09:00
jannauas second compatible
#asahi-dev · 2026-09-08 08:59
jannauwhere? the kernel has "apple,j415-macaudio"
#asahi-dev · 2026-09-08 08:54
chadmedthe combinatorics on this is crazy
#asahi-dev · 2026-09-08 08:53
chadmedi missed it too dont worry
#asahi-dev · 2026-09-08 08:53
chadmedj415
#asahi-dev · 2026-09-08 08:53
chaos_princessdid i screw that up and put a j316 alias there
#asahi-dev · 2026-09-08 08:51
chadmedoh we need to fix the j615 sound compatible to alias a machine with four speakers instead of 6
#asahi-dev · 2026-09-08 07:24
chaos_princess'cause it was
#asahi-dev · 2026-09-08 07:23
yukaand they left already
#asahi-dev · 2026-09-08 07:23
yukawhy does this sound like pasted from a slop generator
#asahi-dev · 2026-09-08 01:38
unoloxiasemantics would be appreciated.
#asahi-dev · 2026-09-08 01:38
unoloxiaStandalone INFO/ONLINE/Ping/Pong works, and I can return naturally from cL4’s kernel bootstrap before starting XNU on the same CPU, but XNU currently stalls after its early Domain 2 TXM calls, before the expected Domain 3/Table 0 SK RingGate call. Pointers on the real SPTM’s second SK entry/handoff
#asahi-dev · 2026-09-08 01:38
unoloxiaSpeakers, 3.5mm out and internal microphone array from J700 achieved without Exclaves required. Successfully booted cL4 (ExclaveOS) as a secondary guest via a SPTM emulator to get traces, although iSight is being difficult. Any ideas on getting SK to talk to XNU via Tightbeam?
#asahi-dev · 2026-09-07 13:13
svenI think it’s just 7.3-rc1
#asahi-dev · 2026-09-07 12:58
JPeisachsven: just so i can review it correctly in full context, the changes in drivers/usb/typec/* are based on usb-next right?
#asahi-dev · 2026-09-07 12:55
JPeisachreviewing the new patches
#asahi-dev · 2026-09-06 18:38
svenhttps://lore.kernel.org/asahi/20260906-b4-apple-soc-tbt-v2-0-1f80085f93fb@kernel.org/
#asahi-dev · 2026-09-06 18:22
svenfixed the rest
#asahi-dev · 2026-09-06 18:17
svens/the/end/ for the port unlock stuff and then it should make sense
#asahi-dev · 2026-09-06 18:07
leio"thunderbold" in cover letter "Changes in v2" (commit 0f3086f40d7), also "insid" -> "inside", don't understand the "Moved port unlock" sentence after that, something is off with it; commit e3cabed33 log probably s/not SVID/no SVID/? In commit bbee15ba6 code comments "The altmode has alreayd" -> already
#asahi-dev · 2026-09-06 18:07
leioWell, now you made me try to find more feedback, but only thing I could really do is nitpicking on English and typos, so feel free to just ignore :)
#asahi-dev · 2026-09-06 17:26
svenguess we need to do the immutable branch dance then for the first two typec commits
#asahi-dev · 2026-09-06 17:26
svenso that means the tipd commit definitely have to go through the usb tree
#asahi-dev · 2026-09-06 17:22
svenugh, true
#asahi-dev · 2026-09-06 17:22
chaos_princesssven: how do you want to resolve my ace3 and your tb stuff conflicting
#asahi-dev · 2026-09-06 17:21
sveni don't mind feedback like that if it's combined with other useful feedback ;)
#asahi-dev · 2026-09-06 17:20
leioit's tb, not tbt! /me hides
#asahi-dev · 2026-09-06 17:11
svenhttps://github.com/AsahiLinux/linux/tree/b4/apple-soc-tbt probably read to go out like this
#asahi-dev · 2026-09-06 17:09
sven 37 files changed, 4529 insertions(+), 132 deletions(-) 🫠
#asahi-dev · 2026-09-06 17:08
svenhah :D
#asahi-dev · 2026-09-06 17:07
yukathe entire "separate_nvmmu_base" thing seems to have been unnecessary. While that's how macOS does it, we can also just use reg[9] for everything and it works
#asahi-dev · 2026-09-06 17:06
yukaWhut
#asahi-dev · 2026-09-06 16:07
yukaThis is a weird situation. The register at this address does different things for <M4 and >=M4 but the same value happens to be reasonable for both
#asahi-dev · 2026-09-06 16:01
yukathat explains how it can work
#asahi-dev · 2026-09-06 16:01
yukaM3 Max fw 27.x also respects qsize
#asahi-dev · 2026-09-06 15:57
yukaAt least I can set a lower value that way
#asahi-dev · 2026-09-06 15:55
yukaOk, so M3 Max fw 14.x respects qsize
#asahi-dev · 2026-09-06 15:47
yukaNot what I expected
#asahi-dev · 2026-09-06 15:46
yukafw 14.x
#asahi-dev · 2026-09-06 15:46
yukaaccording to the crash log
#asahi-dev · 2026-09-06 15:46
yukaOn M3 Max, I/O SQ/CQ size is 16
#asahi-dev · 2026-09-06 15:40
sven22 patches for tbt v2 now :/
#asahi-dev · 2026-09-06 14:52
svendunno how the cq even works then because we should definitely hit its size
#asahi-dev · 2026-09-06 14:51
svenyeah, the submission "queue" is a vector/array here
#asahi-dev · 2026-09-06 14:41
yukabut the completion queue? all the data structures are allocated for size 64, but it would actually use up to 65 entries
#asahi-dev · 2026-09-06 14:40
yukathe submission queue doesn't really matter I guess, since we can just use less than the full size
#asahi-dev · 2026-09-06 14:38
yukaAssuming M3 has the same behavior of setting queue sizes through +0x1210 and being 0's based (and all signs point to that), I wonder how this even works.
#asahi-dev · 2026-09-06 14:27
sventhat's the whole idea behind doing stuff like "M3-nvme", "M1-nvme". that essentially says "This device works with M1-nvme already but may have additional, optional features with M3-nvme"
#asahi-dev · 2026-09-06 14:27
yukaThat's cool

plus ›