Commit 05034dd0 authored by mperes's avatar mperes Committed by nouveau

more changes suggested by imirkin

parent 527d7a88
......@@ -91,7 +91,9 @@ After you obtained the mmiotrace, look for the base offsets used by the firmware
[0] 445.938745 MMIO32 W 0x086110 0x004dd800 PPPP.XFER_EXT_BASE <= 0x4dd80000
$ demmio -f vdpau-mmiotrace | less
/RAMIN32.*4de40000 would get you to the start of the mmiotrace, from my log I could see the RAMIN32 writes end at 4de50918, so I need to grab 4de[45].* for BSP firmware:
/RAMIN32.*4de40000
would get you to the start of the mmiotrace, from my log I could see the RAMIN32 writes end at 4de50918, so I need to grab 4de[45].* for BSP firmware:
$ demmio -f vdpau-mmiotrace 2>&1 | grep 'RAMIN32 .* 4de[45].* <=' | awk '{ print $7 }' | python -c \
"
......@@ -100,6 +102,10 @@ After you obtained the mmiotrace, look for the base offsets used by the firmware
fd.write(struct.pack(\"@I\", int(line.rstrip(), 16)))
"
Alternatively, you can use perl to execute for the last command. It is also more convenient as the same script can be used for all firmwares:
$ demmio -f vdpau-mmiotrace | grep 'RAMIN32 .* 4de[45].* <=' | awk '{ print $7 }' | perl -ne 'print chr(hex(substr($_, 6, 2))), chr(hex(substr($_, 4, 2))), chr(hex(substr($_, 2, 2))), chr(hex(substr($_, 0, 2))),' > fuc084
This was just for PBSP, but the same applies to PVP with fuc085, and PPPP with fuc086. Put the resulting files in /lib/firmware/nouveau/
Offsets may differ, and it is recommended to check you don't end up with too big or too small a file. It *looks* like mine are multiples of 1000 bytes, on the nvidia 310 drivers.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment