Repository navigation
drm/asahi: g15: admit TEXT 125f0497 on J516C and J514C (carry of #340) - #487
Conversation
Two J516C MacBook Pro 16" M3 Max owners (issue #289) load a GPU firmware whose TEXT digest is 125f0497c7904fde... (sha256 125f0497c7904fde87b05a9264a88cf03bdb3572a1715cec91bd0f9b78245544, TEXT 0x64000, DATA 0x140000, marker 0x5cf28). The driver refuses it and the Mac falls back to llvmpipe. Add it as a third FirmwareBuild, written like the two existing J516C entries and still gated to the J516C. The entry name and the comment record where the digest was measured; they do not claim a distinct firmware build. Evidence from #289: with the digest accepted through asahi.g15_accept_text_prefix, glxinfo reports Apple M3 Max (G15C B2), and a GLES compute run shows 0 mismatches and no faults in dmesg. This branch boots on a J516C M3 Max in the Mac lab (job j1031-185713-2fe6, 3 of 3 tests pass, GPU probed). That Mac loads the macOS 14.7 stub firmware, so the new digest itself was not exercised there. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Naeem Malik <malik2015naeem@gmail.com> Signed-off-by: Scott Jones <scottajones@gmail.com>
A 14-inch M3 Max J514C loads the same GPU firmware TEXT that the previous commit admits on J516C: sha256 125f0497c7904fde87b05a9264a88cf03bdb3572a1715cec91bd0f9b78245544, TEXT 0x64000, DATA 0x140000, marker 0x5cf28. Its boot chain reports OS firmware 14.7, iBoot2 iBoot-10151.140.19.700.2 and system firmware 26.6.2 (omacom/omarchy-mac-pkgs#129). Without the digest the driver refuses the firmware and the Mac falls back to llvmpipe. With it accepted through asahi.g15_accept_text_prefix, the GPU came up in all 3 boots tried; in the first, glxinfo reports G15C B2 with OpenGL 4.6 accelerated and the kernel log shows no asahi-g15 errors. Idle only; Vulkan and load were not run. A row takes one machine, so add a second row for the same digest bound to apple,j514c. The J516C row stays bound to apple,j516c; the digest is not open to any other T6031 board. The board images come from the Config, not from the row, so the row carries only the firmware identity. The J514C host test counted exactly one J514C row and expected another board to be refused a digest; with one digest bound to two boards, count two rows and expect the first row bound to the asking board instead. Not tested on hardware by this change: the new digest itself was not exercised in the Mac lab, whose J514C loads the already admitted build. Vulkan, sustained load and power and thermal qualification of J514C remain open. Assisted-by: Claude:claude-sonnet-5-5 Assisted-by: Claude:claude-opus-5-5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Naeem Malik <malik2015naeem@gmail.com> [scott: reworded message and row comment to the one verified J514C case] Signed-off-by: Scott Jones <scottajones@gmail.com>
|
Note Drafted with Claude Opus 5. I read every line and reproduced every number myself before I posted it. No objection to this merge. It unblocks a J514C today, and a boot override is not something a user should have to type. One measurement for the record, because a fourth J516C will arrive. I pulled The segment layout matches all three pinned So The allow-list therefore grows once per machine, not once per build. Every new owner needs a report, a review and a kernel release. What could replace itThe build's own 16-byte One measurement decides whether this works: does the boot chain leave TEXT+0x4214 alone? A I cannot run that measurement. This Mac has no Linux yet, because the T6030 rows are in no release. The parser that produced the table above is 90 lines of Python and runs on any |
Carries #340 by Naeem Malik, who is away. Pushing the requested changes to the PR's own branch was refused, so the same work comes from an omacom branch here. Naeem stays the author of both commits.
Summary
The changes since #340's approved head
b33057c8are the ones asked for in its review: the J514C title, and the message and row comment narrowed to the one verified J514C case. Both commits now carry Scott's Signed-off-by after Naeem's.Evidence
asahi.g15_accept_text_prefix=0x125f0497c7904fde), the GPU comes up: glxinfo reports M3 Max G15C, accelerated GL 4.6. One boot; Vulkan and sustained load not yet tested.Merge Danger
Door: two-way
Blast Radius: small
Only J516C and J514C with this firmware TEXT are affected; every other board's allow-list is unchanged. Supersedes #340.