aboutsummaryrefslogtreecommitdiffstats
path: root/fw/windows_inventory.jsonl (follow)
Commit message (Collapse)AuthorAge
* fw: harvest all 53 Windows driver versions -- 110 new firmware images, 17 TA ↵user2026-09-29
types Ran the download/extract/carve/delete loop over every Adrenalin package for this card, 22.12.1 through 26.7.1, 53 of 53 processed with no failures. Recording a silent failure mode that nearly cost 30 packages: the first run reported "NO amdkmdag.sys" for every version from 23.7.1 onward. The cause is that 22.x-23.5.x are NSIS self-extractors while 23.7.1 and later are PE32+ 7-Zip SFX with the archive embedded around 0x1b3e00, and 7z -tnsis exits cleanly while extracting nothing from those. The harvester now tries both formats and retries versions previously recorded as failed. Dedup needed correcting too. The Windows sys_drv 0.49.0.51 differs from the linux-firmware build of the same version in exactly 256 contiguous bytes at the end of the body, which is the RSA-2048 signature -- identical code, different signature, as expected for randomised PSS. Counting on content excluding that trailing block gives 114 distinct contents from 117 Windows files, 4 overlapping the existing corpus, so 110 genuinely new firmware images rather than the naive count. Two groups inside the Windows set differ only by signature, including three copies of RAS 27.0.0.22, so AMD ships the same image re-signed; that is a useful data point for the rollback finding since multiple valid signatures exist over identical content. The corpus now spans 17 component types and 142 unique bodies, including CSU and OC which only appear in later drivers, so the TA inventory grows across the train. Also corrects the apu tag decode from the first pass, which was byte-reversed: the tags are NV31, NV33, NV24 and MI20. Seven sys_drv builds carry NV31, our exact silicon, and six of them are versions linux-firmware never shipped (0.49.0.35/.38/.40/.42/.46/.53), interleaving with the Linux set to give a near-contiguous .35 to .54 range for version diffing. No sOS images appear in Windows packages. Bodies, full signed containers, per-driver records and manifest hashes are all stashed.