Repository navigation
extract-vendor-firmware: the Pixel 7's video codec firmware - #747
Conversation
With -d panther, also copy /vendor/firmware/mfc_fw.bin to s5p-mfc-v15.fw, the name mainline's s5p-mfc requests for the gs201 MFC (linux-omarchy-mobile#250). It is the MFC's RISC core firmware, plain and unsigned; the check is that it starts with that core's vector table (eight ARM branches) and is whole words, and the run reports its last word, the version the MFC reports in FW_VERSION once it runs. Tested on the Pixel 7's factory image CP3A.261005.002.A1: the staged s5p-mfc-v15.fw is the same file the phone decodes with (sha256 766030515ddc53bc...), reports 0x44250901, and with only that copy, in /usr/lib/firmware/updates on the phone, derekross#250's s5p-mfc decodes a 1080p H.264 stream bit-exact. tests/extract-vendor-firmware: 36 ok; against main's tool the five new checks fail, and without the vector table check its refusal test fails. Only panther: cheetah has the same SoC, but no MFC node yet. I used AI help (Claude) to work on this.
|
Thank you, this is a clean firmware mapping, and a really good test record: the staged file is the very one your Pixel 7 decodes with, and the version the tool prints is the one the MFC reports. I checked the name against #250 ( One small thing for the commit: CONTRIBUTING asks for a I'll merge it. It does nothing on a phone until #250 lands, which is fine: the file just waits in |
|
Sorry for missing your question, Derek. It was Claude Opus 5.5 (Anthropic). The trailer is |
The firmware side of derekross/linux-omarchy-mobile#250 (hardware H.264 decode on the Pixel 7). With
-d panther, the toolalso copies
/vendor/firmware/mfc_fw.bintousr/lib/firmware/updates/s5p-mfc-v15.fw, the name mainline's s5p-mfcrequests for the gs201 MFC. Nothing of Google's goes into the repo: as with the Wi-Fi and audio files, each owner
takes it from their own factory image.
The file is the MFC's RISC core firmware, plain and unsigned. The sanity check is that it starts with that core's
vector table (eight ARM branch instructions) and is a whole number of words. The run prints its last word, which is
the version the MFC reports in FW_VERSION once the firmware runs.
Tested:
s5p-mfc-v15.fwis the same file my phone decodes with(sha256
766030515ddc53bc…), and the run printsVideo codec firmware: s5p-mfc-v15.fw (version 0x44250901),the value the MFC reports.
/usr/lib/firmware/updates(none in/usr/lib/firmware), s5p-mfc from linux-omarchy-mobile#250loads it and decodes a 1080p H.264 High stream bit-exact against FFmpeg's software decode (300 frames, ~71 fps).
tests/extract-vendor-firmware: 36 ok. Three new checks: a panther run stages the file and reports its version,and a firmware without the vector table and a missing
mfc_fw.binare both refused, with the previous outputs leftas they were. Negative controls: with main's tool, the five new checks fail; with the vector-table check removed,
its refusal test fails.
tools/pr-checkandtests/tools-helppass.Not checked:
I used AI help (Claude) to work on this.