Displaying 4 results from an estimated 4 matches for "ref_bo".
Did you mean:
ref_bh
2013 Dec 07
3
[PATCH] nv50: enable H.264 for NV98+ (VP3, VP4.0)
Create the ref_bo without any storage type flags set for now. This can
probably be split up somehow later on, but this seems to work.
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
Cc: "10.0" <mesa-stable at lists.freedesktop.org>
---
Would be great if someone could see if this also mak...
2013 Dec 08
2
[PATCH 1/3] nv50: enable h264 and mpeg4 for nv98+ (vp3, vp4.0)
Create the ref_bo without any storage type flags set for now. The issue
probably arises from our use of the additional buffer space at the end
of the ref_bo. It should probably be split up in the future.
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
Tested-by: Martin Peres <martin.peres at labri.fr&...
2013 Aug 11
10
[PATCH 00/10] Add support for MPEG2 and VC-1 on VP3/VP4 for NV98-NVAF
As it turns out, with the proprietary firmware, the VP3 and VP4 interfaces are
identical. Furthermore, this is all already implemented for nvc0. So these
patches (a) move the easily sharable bits of the nvc0 implementation into the
nouveau directory, and then (b) implement the other parts in nv50. The
non-shared parts are still largely copies, but there are some differences, not
the least of which
2013 Dec 07
1
H.264 engine differences between fermi and tesla cards
On Fri, Dec 6, 2013 at 7:36 PM, Benjamin Morris <bmorris at nvidia.com> wrote:
> I've gathered a few hints regarding H264 video decoding on our hardware. Hopefully some of them will be useful.
Very useful!
>
> First off, regarding naming in general. Our internal names for our video engines differ from the names you've been using. Below is a translation map between the