#
#asahi-dev · 2026-11-03 00:58
Youwes09You can shoot me an email at yuvi.shen@outlook.com
#asahi-dev · 2026-11-03 00:58
Youwes09Would you like me to email you the patch?
#asahi-dev · 2026-11-03 00:57
myriahow did you manage that though, if I can ask?
#asahi-dev · 2026-11-03 00:57
Youwes09myria: one catch with that: M1/M2 events are only 8 bits and the driver masks them, so on an M1 perf will accept something like r182 and just count 0x82 without complaining. I kept separate 8 and 16 bit formats for that reason...
#asahi-dev · 2026-11-03 00:56
Youwes09myria: saw your messages. looks like you already switched to config:0-15 for everyone, so my diff isn't needed anymore
#asahi-dev · 2026-11-03 00:02
JamesCalligeros[m]thanks!
#asahi-dev · 2026-11-03 00:02
MichaelReeves[m]No problem, here https://drive.google.com/drive/folders/1UDeoxf9VtCyi-lpMrXROD2epa9Q27ZFk
#asahi-dev · 2026-11-02 23:59
JamesCalligeros[m]Michael Reeves: would you mind sharing the FNV screenshots again? sorry.
#asahi-dev · 2026-11-02 23:47
myriaAlso, can you send me through a name/email if you see this and are comfortable with that? Just to add a tested-by tag if you're happy otherwise
#asahi-dev · 2026-11-02 23:44
myriadoesn't seem like older m2 devices should have problems if I just declare the the first 16 bytes are the config, so I may just use `config:0-15` for everyone
#asahi-dev · 2026-11-02 23:43
myriaCurrently, it looks like the naming of the format attrs means that you can only have one per file, otherwise they'll name clash, or you need to expand some of the macros themselves
#asahi-dev · 2026-11-02 23:42
myria(so if you ever see this, please send it through)
#asahi-dev · 2026-11-02 23:42
myriaYouwes09: though you seem to have left the channel, I would love to see your diff, and thank you so much for testing!
#asahi-dev · 2026-11-02 23:41
myriajannau: Does the new avd patches require the new firmware, have we moved more of the work onto the CM3? I think I vaguely remember sofus talking about getting more work to be done there
#asahi-dev · 2026-11-02 21:05
svenright now I just take the trustcache that has the same prefix as the single integrity thingy but I bet that's just listed in BuildManifest as well then
#asahi-dev · 2026-11-02 21:04
sventhere's a bunch of trustcaches but only one integrity_catalog
#asahi-dev · 2026-11-02 21:03
svenyeah, that and something called "trustcache" and "integrity_catalog"
#asahi-dev · 2026-11-02 21:02
nicolas17they should be in the BuildManifest.plist yeah
#asahi-dev · 2026-11-02 21:02
nicolas17exclavecore?
#asahi-dev · 2026-11-02 21:01
svenI bet they are just listed in some plist or whatever
#asahi-dev · 2026-11-02 20:59
sveneven better. "just" needs some logic to find the right files inside the ipsw then
#asahi-dev · 2026-11-02 20:43
jannau`python3 -m urlcache $IPSW $FILES` in asahi-installer/src should work
#asahi-dev · 2026-11-02 20:39
svenor at least collects them from the preboot volume automatically
#asahi-dev · 2026-11-02 20:39
svenif anyone wants to shave a yak: it might be useful to write a small python script that calls into ipsw --remote to extract all those blobs from an .ipsw file
#asahi-dev · 2026-11-02 20:37
svenhttps://github.com/AsahiLinux/docs/pull/287 tested on m5, a18 pro will probably panic somewhere in early boot before snooze6214[m]'s fix
#asahi-dev · 2026-11-02 19:35
flokli(on our side)
#asahi-dev · 2026-11-02 19:33
flokliI might just wait for that to get picked, none of this is currently exposed yet.
#asahi-dev · 2026-11-02 19:32
flokliAh thanks, so not in a tagged kernel yet. I was just very confused
#asahi-dev · 2026-11-02 19:32
jannauhttps://forge.fedoraproject.org/asahi/avd-fw has compattibility patches to provide the config at the place asahi-7.2.* kernels expect it
#asahi-dev · 2026-11-02 19:31
jannauflokli: no that was done before we settled on the change in the firmware, https://github.com/AsahiLinux/linux/commit/faf8d1233a82cff11182dc7e83bcdd356f5feb83 does read from 0x400
#asahi-dev · 2026-11-02 19:27
floklijannau: https://github.com/AsahiLinux/linux/commit/2e6ef8294919b4bd7b23756d836b447b0b4ffb5f doesn't seem to read from the 0x400 offset that https://github.com/AsahiLinux/avd-fw/commit/79854f31bd4809d78fef49167b8eccfe676b6010 claims, or am I holding this wrong?
#asahi-dev · 2026-11-02 17:47
jannaualso switched to the v3 upstream avd DTS and fixed 1 compatibility issue with the current fw, there might be more, I did not test thouroughly
#asahi-dev · 2026-11-02 17:44
jannauI dropped a few patches which I believe are no longer necessary. power-domain or less likelydart issue might be caused by that
#asahi-dev · 2026-11-02 17:41
jannauI've updated asahi-wip and the bits branches to v7.3 and picked devicetree changes up. bits/000-devicetree has almost 250 commits
#asahi-dev · 2026-11-02 15:58
Youwes09myria: the 16-bit table also points at event_8b, so M3/M4 only show config:0-7 and perf warns on events like r182. I fixed it here by keeping both named event with __ATTR(event, 0444, event_16b_show, NULL), cycles and instructions work after that. Happy to send the diff if you want it!
#asahi-dev · 2026-11-02 15:57
Youwes09myria: found one bug in "Support per-implementation event size". PMU_FORMAT_ATTR(event_8b, ...) names the sysfs file event_8b instead of event, so perf can't parse event= anymore and the cycles/instructions aliases break on every chip, M1 too. raw rXXXX still works which is why sleep 5 didn't show it...
#asahi-dev · 2026-11-02 15:56
Youwes09myria: tested the PR on my M4 Air (J713), 7.4-rc1. all 60 M4 events count on both P and E cores, two counters on the same event always match exactly, all 10 counters at once work, and perf record works on both clusters!
#asahi-dev · 2026-11-02 15:54
svenoh right, totally forgot that existed! thanks!
#asahi-dev · 2026-11-02 15:12
yukaOr the google docs patch tracker
#asahi-dev · 2026-11-02 15:12
yukaCheck the links in this pad
#asahi-dev · 2026-11-02 15:12
yukahttps://pad.yuka.dev/Iu1II_aFRRy8G1p4hr2qnA
#asahi-dev · 2026-11-02 15:12
myriaalso, gentle poke to resend #7 of https://lore.kernel.org/asahi/20260829-b4-tbt-fixes-v3-0-e1fab6ac54fe@kernel.org/ now that 7.4-rc1 is out, if you have the time
#asahi-dev · 2026-11-02 15:09
myriahttps://lore.kernel.org/asahi/20261018-apple-sartv4-v1-0-1eaa5d63f6a2@cyberchaos.dev/T/#t
#asahi-dev · 2026-11-02 15:08
svenfor the dt-style-check: does that need a new version because the checker changed or is it still fine?
#asahi-dev · 2026-11-02 15:08
svendo you have a link or message id?
#asahi-dev · 2026-11-02 15:07
svenif dt is acked I can review SART myself and just merge it
#asahi-dev · 2026-11-02 15:07
myriaA18 I2C and pinctrl is waiting on review
#asahi-dev · 2026-11-02 15:06
myriaM5 sart might be good? dt has been acked, not sure about soc requirements though
#asahi-dev · 2026-11-02 15:05
myriathis one maybe: https://lore.kernel.org/asahi/20260924-apple-dts-m4-dt-style-check-v1-0-3ec651d75baf@cyberchaos.dev/
#asahi-dev · 2026-11-02 14:47
jannauhttps://patch.msgid.link/20260925-apple-m3-nvme-v1-0-5e832e2f4aa9@jannau.net

plus ›