search for: nv84_vp

...re from the blob and tried playing a video with mplayer. It played ok for a few minutes (albeit with noticeable artifacts), then the gpu locked up - I could only switch to a vt and reboot. The video codec is H264 - MPEG-4 AVC (part 10), 1920x802. $ ls /lib/firmware/nouveau nv84_bsp nv84_bsp-h264 nv84_vp nv84_vp-h264-1 nv84_vp-h264-2 nv84_vp-mpeg12 nv84_vp-vc1-1 nv84_vp-vc1-2 nv84_vp-vc1-3 nv84_xuc00f nv84_xuc103 $ vdpauinfo display: :0 screen: 0 API version: 1 Information string: G3DVL VDPAU Driver Shared Library version 1.0 Video surface: name width height types -------------------...

...screen->firmware_info.profiles_present |= FIRMWARE_BSP_KERN; + nouveau_object_del(&obj); + screen->firmware_info.profiles_checked |= FIRMWARE_BSP_KERN; + } + + if (!FIRMWARE_PRESENT(checked, VP_H264_1)) { + ret = stat("/lib/firmware/nouveau/nv84_vp-h264-1", &s); + if (!ret && s.st_size > 1000) + screen->firmware_info.profiles_present |= FIRMWARE_VP_H264_1; + screen->firmware_info.profiles_checked |= FIRMWARE_VP_H264_1; + } + + /* should probably check the others, but assume that 1...

...style, >> which is nv$chipset_fuc$offset. However here, all the chips share >> the same firmware. Also the offset would be 103 vs 00f, and is a >> little arbitrary. (And fuc doesn't apply here... xt? xtensa?) I've >> left it the way I had it: nv84_bsp and nv84_vp. >> >> 3. Firmware load time. I chose to load the fw into memory in the ctor, >> and then copy it in in init, due to some potentially bogus >> suspend/resume concerns. Also e.g. mplayer likes to create/destroy >> decoders at startup a few times. The downside i...

...suggested to use the falcon naming style, which is nv$chipset_fuc$offset. However here, all the chips share the same firmware. Also the offset would be 103 vs 00f, and is a little arbitrary. (And fuc doesn't apply here... xt? xtensa?) I've left it the way I had it: nv84_bsp and nv84_vp. 3. Firmware load time. I chose to load the fw into memory in the ctor, and then copy it in in init, due to some potentially bogus suspend/resume concerns. Also e.g. mplayer likes to create/destroy decoders at startup a few times. The downside is that ~200KB of memory is gone. Let me k...

...gt; which is nv$chipset_fuc$offset. However here, all the chips share >>> the same firmware. Also the offset would be 103 vs 00f, and is a >>> little arbitrary. (And fuc doesn't apply here... xt? xtensa?) I've >>> left it the way I had it: nv84_bsp and nv84_vp. >>> >>> 3. Firmware load time. I chose to load the fw into memory in the ctor, >>> and then copy it in in init, due to some potentially bogus >>> suspend/resume concerns. Also e.g. mplayer likes to create/destroy >>> decoders at startup a few t...

...e falcon naming style, > which is nv$chipset_fuc$offset. However here, all the chips share > the same firmware. Also the offset would be 103 vs 00f, and is a > little arbitrary. (And fuc doesn't apply here... xt? xtensa?) I've > left it the way I had it: nv84_bsp and nv84_vp. > > 3. Firmware load time. I chose to load the fw into memory in the ctor, > and then copy it in in init, due to some potentially bogus > suspend/resume concerns. Also e.g. mplayer likes to create/destroy > decoders at startup a few times. The downside is that ~200KB of &gt...

On Fri, Feb 13, 2015 at 9:52 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Fri, Feb 13, 2015 at 8:59 PM, Andy Lutomirski <luto at amacapital.net> wrote: >> My new GTX 960 (GM206, I think) says: >> >> [ 10.329351] nouveau ![ DEVICE][0000:09:00.0] unknown Maxwell chipset >> [ 10.329355] nouveau E[ DEVICE][0000:09:00.0] unknown chipset, 0x126010a1

...nv84_load_firmwares( + dev, dec, "/lib/firmware/nouveau/nv84_bsp-h264", NULL); +} + +static struct nouveau_bo * +nv84_load_vp_firmware(struct nouveau_device *dev, struct nv84_decoder *dec) +{ + return nv84_load_firmwares( + dev, dec, + "/lib/firmware/nouveau/nv84_vp-h264-1", + "/lib/firmware/nouveau/nv84_vp-h264-2"); +} + +static struct nouveau_bo * +nv84_load_vp_firmware_mpeg(struct nouveau_device *dev, struct nv84_decoder *dec) +{ + return nv84_load_firmwares( + dev, dec, "/lib/firmware/nouveau/nv84_vp-mpeg12", NULL...

...es the card work. (Definitely no acceleration > without signed firmware for now though.) The driver loads and seems to work. The nouveau X driver doesn't load, though. I tried to use the nvidia firmware: $ ls -l /lib/firmware/nouveau/ total 380 -rw-r--r--. 1 root root 110188 Mar 17 15:29 nv84_vp -rw-r--r--. 1 root root 110188 Mar 17 15:29 nv84_xuc00f -rw-r--r--. 1 root root 6400 Mar 17 15:29 vuc-h264-0 -rw-r--r--. 1 root root 3072 Mar 17 15:29 vuc-mpeg12-0 -rw-r--r--. 1 root root 7424 Mar 17 15:29 vuc-mpeg4-0 -rw-r--r--. 1 root root 7424 Mar 17 15:29 vuc-mpeg4-1 -rw-r--r--. 1 root...

...nv84_load_firmwares( + dev, dec, "/lib/firmware/nouveau/nv84_bsp-h264", NULL); +} + +static struct nouveau_bo * +nv84_load_vp_firmware(struct nouveau_device *dev, struct nv84_decoder *dec) +{ + return nv84_load_firmwares( + dev, dec, + "/lib/firmware/nouveau/nv84_vp-h264-1", + "/lib/firmware/nouveau/nv84_vp-h264-2"); +} + +static struct nouveau_bo * +nv84_load_vp_firmware_mpeg(struct nouveau_device *dev, struct nv84_decoder *dec) +{ + return nv84_load_firmwares( + dev, dec, "/lib/firmware/nouveau/nv84_vp-mpeg12", NULL...

..._identify(struct nouveau_device *device) device->oclass[NVDEV_ENGINE_FIFO ] = &nv84_fifo_oclass; device->oclass[NVDEV_ENGINE_SW ] = &nv50_software_oclass; device->oclass[NVDEV_ENGINE_GR ] = &nv50_graph_oclass; - device->oclass[NVDEV_ENGINE_VP ] = &nv84_vp_oclass; + device->oclass[NVDEV_ENGINE_VP ] = &nv98_vp_oclass; device->oclass[NVDEV_ENGINE_CRYPT ] = &nv98_crypt_oclass; - device->oclass[NVDEV_ENGINE_BSP ] = &nv84_bsp_oclass; + device->oclass[NVDEV_ENGINE_BSP ] = &nv98_bsp_oclass; device->oclass[N...