#
#asahi-dev · 2026-05-11 18:15
janekt2000[m]chaos_princess: is this what you start with for install or do you need to first do something else?
#asahi-dev · 2026-05-11 16:27
habibyo/
#asahi-dev · 2026-05-11 08:20
fl0_idu154ss that's a question for #asahi-alt or wherever asahi debian peopl hang around
#asahi-dev · 2026-05-11 07:54
u154ssHello all. A MESA question. Running Debian on an M2 Pro. The "current" MESA version seems to be pinned at 20250425. Is there a newer version? TIA.
#asahi-dev · 2026-05-10 22:16
StanfordAppliedCyber[m]i'll add however that the biggest thing in our favor i that sptm mediates all interactions between gl and el, so ultimately the surface we need to emulate can be reduced to a relatively small set of calls + the sptm handoff
#asahi-dev · 2026-05-10 22:15
StanfordAppliedCyber[m]most of the exclave plumbing is in place on the m4
#asahi-dev · 2026-05-10 22:15
StanfordAppliedCyber[m]also, re: m5, exclaves will be annoying but i'm far more optimistic about "just run them as a separate guest" because sk and the exclae userspace are meant to run under the sptm hypervisor in GL, whereas sptm is itself effectively a hypervisor --> it's snowflaky. for exclaves, secure kernel, and other m5 stuff, my first approach would be second guest as opposed to full emulation, at least based off my current understanding.
#asahi-dev · 2026-05-10 21:27
StanfordAppliedCyber[m]apparently there's evidence the amx gate is just a sysctl, i can investigate this pretty easily just by togging the value and then seeing what amx workloads do
#asahi-dev · 2026-05-10 21:05
StanfordAppliedCyber[m]parts of this are definitely upstreamable ignoring sptm because among other things i'm adding support for 26.4.1, and i'm optimistic we can find a copyright friendly way of getting the sptm emulation here
#asahi-dev · 2026-05-10 21:04
StanfordAppliedCyber[m]thanks for the help and feedback on the approach @ sven @ other asahi devs who chimed in, will keep yall updated with where i make it
#asahi-dev · 2026-05-10 18:00
sveniirc the parses took data packets exported from wireshark as json
#asahi-dev · 2026-05-10 17:59
svenmy plan was to write something that watches for apple debug devices and then uses FUSE/CUSE to expose some /dev/tty.applekis.whatever devcies
#asahi-dev · 2026-05-10 17:58
svenhttps://f.svpe.de/2f3b03f14a51fea811f6edc9685b92599558ccb7c08a6ba85039800983fc2703_kis.py.txt
#asahi-dev · 2026-05-10 17:57
svenah, looks like the python code is even on this machine that i have with me: https://f.svpe.de/94abc21820b8833bce0fec48dac352e99138910b23dddcd83d644a84bc629a9b_kis-test.py.txt
#asahi-dev · 2026-05-10 17:53
svenwhen i tried with wireshark on macos half of the messages from the host were missing
#asahi-dev · 2026-05-10 17:47
yukathe traces I got look quite complete
#asahi-dev · 2026-05-10 17:29
svennot any working code, but i can upload the full traces i have and my python parser for those
#asahi-dev · 2026-05-10 17:28
svenyuka: remind me tomorrow evening and i can push the stuff i have somewhere
#asahi-dev · 2026-05-10 17:28
svenyuka: wireshark doesn't capture the full thing because macos is dumb, you need a real usb analyzer
#asahi-dev · 2026-05-10 17:27
svennickchan: nested virt. put SPTM into GL1/fake-GL2 and the exclave kernel into real GL1 and m1n1 into real GL2
#asahi-dev · 2026-05-10 16:02
mazit is odd that macvdmtool doesn't work, since that's one of CS's ancestors...
#asahi-dev · 2026-05-10 16:01
jannauset 2 is sbu
#asahi-dev · 2026-05-10 16:01
mazah, true. that's set 2 (can't remember what the code is like)
#asahi-dev · 2026-05-10 15:59
jannauand 0x01840306 is SBU1/SBU2 as well
#asahi-dev · 2026-05-10 15:58
jannauyuka: cs-sw does not send 0x01800306, it mixes in the variable serial pins in. see `vdm[1] |= 1 << (cxt->serial_pin_set + 16);`
#asahi-dev · 2026-05-10 15:54
mazyuka: CS defaults to using the SBU lines to serial. I suspect that macdvmtool is using the secondary set of USB2 lines.
#asahi-dev · 2026-05-10 14:31
yukain other news: I captured some debugusb interactions on mac os using wireshark and am trying to recreate them under linux
#asahi-dev · 2026-05-10 14:30
yukait falls under "Bit mask of lines to map to this action" according to https://asahilinux.org/docs/hw/soc/usb-pd/
#asahi-dev · 2026-05-10 14:30
yukaI'm not sure what this bit does
#asahi-dev · 2026-05-10 14:29
yukathis is the difference
#asahi-dev · 2026-05-10 14:28
yukathe macvdmtool sends 0x5AC8012, 0x01840306
#asahi-dev · 2026-05-10 14:28
yukathe cs-sw sends 0x5AC8012, 0x01800306
#asahi-dev · 2026-05-10 14:27
yukaWe encountered the M4 Pro and M5 Max not allowing enabling serial using macvdmtool, but it was possible using central scrutinizer
#asahi-dev · 2026-05-10 14:14
nickchanwould at least allow the logic to continue working if say m6 doesn't carry any wdt changes this way
#asahi-dev · 2026-05-10 14:05
nickchanalso you are checking the wdt's node variable `node` and not `node_arm_io`
#asahi-dev · 2026-05-10 14:04
nickchanhence mentioning wdt-version as a metric for whether secondary watchdog exists
#asahi-dev · 2026-05-10 14:03
nickchanflokli: basically what I thought is it is always best to disarm the secondary watchdog regardless of whether it is neccessary and don't print bogus messages on SoCs without the secondary watchdog
#asahi-dev · 2026-05-10 13:59
floklii have a J773s here where I had to disable the secondary wd
#asahi-dev · 2026-05-10 13:58
floklibut the ADT lies
#asahi-dev · 2026-05-10 13:58
flokliwell, not M4 Max, M4 Pro
#asahi-dev · 2026-05-10 13:58
floklinickchan: yes
#asahi-dev · 2026-05-10 13:58
nickchanflokli: have you checked writing to wdt reg[2] helped with the device not resetting on M4 Max
#asahi-dev · 2026-05-10 13:57
flokliok, I'm successfully confused now :D
#asahi-dev · 2026-05-10 13:56
nickchanso I assumed it worked fine
#asahi-dev · 2026-05-10 13:56
nickchanno, I just see jannau committing logic that triggers on t8103
#asahi-dev · 2026-05-10 13:56
flokli(even though it might not be necessary)
#asahi-dev · 2026-05-10 13:56
floklidid you test current m1n1 with t8103, is writing to the secondary wd ok there as well?
#asahi-dev · 2026-05-10 13:55
nickchanflokli: Right, wdt-version is only 1 on T8030 and earlier SoCs
#asahi-dev · 2026-05-10 13:55
nickchannot the pro/max
#asahi-dev · 2026-05-10 13:55
nickchanand it seems that the current logic applied to all baseline M-series SoCs

plus ›