From: "Xiang, Haihao" <haihao.xiang@intel.com>
To: "randy.li@rock-chips.com" <randy.li@rock-chips.com>,
"libva@lists.freedesktop.org" <libva@lists.freedesktop.org>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Libva] keep Nalu start code in VASliceDataBufferType data
Date: Wed, 31 Aug 2016 01:52:17 +0000 [thread overview]
Message-ID: <1472608336.17482.50.camel@intel.com> (raw)
In-Reply-To: <30d33872-967b-08d9-fbe9-0d9816fb934e@rock-chips.com>
On Tue, 2016-08-30 at 08:59 +0800, Randy Li wrote:
> Hi all:
> When I just doing the driver for us chip, we would request the
> Nalu
> header present in the data to be process. But I found the data be
> Rendered to with type VASliceDataBufferType is removed the Nalu start
> code. Is there any way to make the client send the data without
> remove
> the start code ? Thank you.
Do you mean the start code prefix 0x000001? It depends on the codec,
VA-API has this requirement for HEVC, but no for AVC.
For AVC, I don't think the existing softwares using vaapi send the
prefix to driver, you have to workaround it in your driver. but if the
application is developed by yourself, you may send the prefix with
setting the right slice_data_offset, so other drivers can work well
with your application.
>
> P.S Thank you for the Intel guys help, I decided not to use the DRM
> framework to implement the interface in kernel after I talked to the
> kernel upstream. But the request API would be used.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-31 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 0:59 keep Nalu start code in VASliceDataBufferType data Randy Li
2016-08-31 1:52 ` Xiang, Haihao [this message]
2016-08-31 2:31 ` [Libva] " Randy Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1472608336.17482.50.camel@intel.com \
--to=haihao.xiang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=libva@lists.freedesktop.org \
--cc=randy.li@rock-chips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.