search for: h264_picparm_vp

Displaying 5 results from an estimated 5 matches for "h264_picparm_vp".

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> Cc: "10.0" <mesa-stable at lists.freedesktop.org> ---
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
...d. Or perhaps the fw-cutter has an insufficiently-precise signature... I'll check it out later.) I will look at your comments on our picparm data structure and will adjust our code. Hopefully that's all that's needed. Thanks again! -ilia > > Thanks, > Ben > > struct h264_picparm_vp { // 700..a00 > uint16_t width, height; > uint32_t stride1, stride2; // 04 08 > uint32_t ofs[6]; // 0c..24 in-image offset > > uint32_t u24; // nfi ac8 ? -> ColocBufferSize > uint32_t bucket_size; // 28 bucket size > uint32_t i...
2013 Nov 30
2
H.264 engine differences between fermi and tesla cards
On Thu, Nov 21, 2013 at 5:22 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Thu, Nov 21, 2013 at 5:07 PM, Benjamin Morris <bmorris at nvidia.com> wrote: >> On 11/19/2013 08:16 PM, Ilia Mirkin wrote: >>> Hello, >>> >>> I hope this is an appropriate style of request for this forum. I added >>> code to support video decoding on the tesla
2013 Dec 07
0
H.264 engine differences between fermi and tesla cards
...ror resilience/concealment may simply be masking the problem on MSDEC3. Below I've filled in our names for unnamed fields in that structure. Hopefully this allows you to make some quick progress; you can apply the same logic you already have for G84 to your G98 code path. Thanks, Ben struct h264_picparm_vp { // 700..a00 uint16_t width, height; uint32_t stride1, stride2; // 04 08 uint32_t ofs[6]; // 0c..24 in-image offset uint32_t u24; // nfi ac8 ? -> ColocBufferSize uint32_t bucket_size; // 28 bucket size uint32_t inter_ring_data_size; // 2c unsigned f0 : 1; // 0 0x01: into 640 shifted by...