Unlike the firmware you need above, there is no requirement on version. Up to nvidia 310.* will likely work. Newer versions are untested, but should still work.
== Extracting kernel video firmware on fermi and kepler. ==
There are 2 sets of firmware for video decoding, one for kernel and one for userspace. Only nvc0 series need the userspace firmware. Kepler, and also nvd9 do '''NOT''' have userspace firmware.
The kernel parts can be obtained by doing a mmiotrace of a program using vdpau for video decoding, for example mplayer -vc ffmpeg12vdpau,ffh264vdpau,ffwmv3vdpau,ffvc1vdpau,ffodivxvdpau, somefile.mkv
After you obtained the mmiotrace, look for the base offsets used by the firmware:
[0] 437.753081 MMIO32 W 0x084110 0x004de400 PBSP.XFER_EXT_BASE <= 0x4de40000
[0] 445.278672 MMIO32 W 0x085110 0x004dde00 PVP.XFER_EXT_BASE <= 0x4dde0000
[0] 445.938745 MMIO32 W 0x086110 0x004dd800 PPPP.XFER_EXT_BASE <= 0x4dd80000
$ demmio 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:
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.
----
== Extracting userspace video firmware on nvc0 series (fermi) (NOT NVD9!!) ==
Requirements:
* libvdpau-dev, libpciaccess-dev, libx11-dev
* [[Valgrind-mmt|valgrind-mmt]]
* build a recent envytools.git, and go to envytools.git/vdpow directory
* with nvidia drivers enabled and X server running, do:
Unlike the firmware you need above, there is no requirement on version. Up to nvidia 310.* will likely work. Newer versions are untested, but should still work.
## Extracting kernel video firmware on fermi and kepler.
There are 2 sets of firmware for video decoding, one for kernel and one for userspace. Only nvc0 series need the userspace firmware. Kepler, and also nvd9 do **NOT** have userspace firmware.
The kernel parts can be obtained by doing a mmiotrace of a program using vdpau for video decoding, for example mplayer -vc ffmpeg12vdpau,ffh264vdpau,ffwmv3vdpau,ffvc1vdpau,ffodivxvdpau, somefile.mkv
After you obtained the mmiotrace, look for the base offsets used by the firmware:
[0]437.753081 MMIO32 W 0x084110 0x004de400 PBSP.XFER_EXT_BASE <= 0x4de40000
[0]445.278672 MMIO32 W 0x085110 0x004dde00 PVP.XFER_EXT_BASE <= 0x4dde0000
[0]445.938745 MMIO32 W 0x086110 0x004dd800 PPPP.XFER_EXT_BASE <= 0x4dd80000
$ demmio 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:
Offsetsmaydiffer,anditisrecommendedtocheckyoudon'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.
---
## Extracting userspace video firmware on nvc0 series (fermi) (NOT NVD9!!)
Requirements:
* libvdpau-dev, libpciaccess-dev, libx11-dev
* [[valgrind-mmt|Valgrind-mmt]]
* build a recent envytools.git, and go to envytools.git/vdpow directory
* with nvidia drivers enabled and X server running, do: