From: Maxime Ripard <maxime.ripard@bootlin.com>
To: ayaka <ayaka@soulik.info>
Cc: hans.verkuil@cisco.com, acourbot@chromium.org,
sakari.ailus@linux.intel.com,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
jenskuske@gmail.com, linux-sunxi@googlegroups.com,
linux-kernel@vger.kernel.org, tfiga@chromium.org,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Chen-Yu Tsai <wens@csie.org>,
posciak@chromium.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Guenter Roeck <groeck@chromium.org>,
nicolas.dufresne@collabora.com,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH v2 1/2] media: uapi: Add H264 low-level decoder API compound controls.
Date: Thu, 17 Jan 2019 12:21:50 +0100 [thread overview]
Message-ID: <20190117112150.qfzqjdmrqpcjqvnh@flea> (raw)
In-Reply-To: <2e734dd6-d459-9990-61fe-27301df35ff7@soulik.info>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
Hi,
On Thu, Jan 10, 2019 at 09:33:01PM +0800, ayaka wrote:
> I forget a important thing, for the rkvdec and rk hevc decoder, it would
> requests cabac table, scaling list, picture parameter set and reference
> picture storing in one or various of DMA buffers. I am not talking about the
> data been parsed, the decoder would requests a raw data.
>
> For the pps and rps, it is possible to reuse the slice header, just let the
> decoder know the offset from the bitstream bufer, I would suggest to add
> three properties(with sps) for them. But I think we need a method to mark a
> OUTPUT side buffer for those aux data.
I'm not sure this is something we actually want. The whole design
decision was that we wouldn't have a bitstream parser in the kernel,
and doing as you suggest goes against that design.
And either if it is something that turns out to be useful, this is
really out of scope for this series.
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-01-17 11:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 14:56 [PATCH v2 0/2] media: cedrus: Add H264 decoding support Maxime Ripard
2018-11-15 14:56 ` [PATCH v2 1/2] media: uapi: Add H264 low-level decoder API compound controls Maxime Ripard
2018-11-27 17:23 ` [linux-sunxi] " Jernej Škrabec
2018-11-28 15:52 ` Maxime Ripard
2018-12-05 12:56 ` Hans Verkuil
2019-01-08 9:52 ` Randy 'ayaka' Li
2019-01-08 17:01 ` ayaka
2019-01-10 13:33 ` ayaka
2019-01-17 11:21 ` Maxime Ripard [this message]
2019-01-17 11:16 ` Maxime Ripard
2019-01-17 11:01 ` Maxime Ripard
2019-01-20 12:48 ` ayaka
2019-01-24 14:23 ` Maxime Ripard
2019-01-24 14:37 ` Ayaka
2019-01-25 12:47 ` Maxime Ripard
2019-01-28 5:54 ` Alexandre Courbot
2018-11-15 14:56 ` [PATCH v2 2/2] media: cedrus: Add H264 decoding support Maxime Ripard
2018-11-24 20:43 ` [linux-sunxi] " Jernej Škrabec
2018-11-27 15:50 ` Maxime Ripard
2018-11-27 16:30 ` Jernej Škrabec
2018-11-27 20:19 ` Jernej Škrabec
2018-11-30 7:30 ` Maxime Ripard
2018-11-30 17:56 ` Jernej Škrabec
2018-11-30 12:37 ` Paul Kocialkowski
2018-12-05 22:27 ` [linux-sunxi] " Jernej Škrabec
2018-11-16 7:04 ` [PATCH v2 0/2] " Tomasz Figa
2018-11-19 14:12 ` Maxime Ripard
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=20190117112150.qfzqjdmrqpcjqvnh@flea \
--to=maxime.ripard@bootlin.com \
--cc=acourbot@chromium.org \
--cc=ayaka@soulik.info \
--cc=groeck@chromium.org \
--cc=hans.verkuil@cisco.com \
--cc=jenskuske@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=nicolas.dufresne@collabora.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=posciak@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wens@csie.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).