From: Thierry Reding <thierry.reding@gmail.com>
To: Nicolas Dufresne <nicolas@ndufresne.ca>
Cc: Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Tomasz Figa <tfiga@chromium.org>,
Alexandre Courbot <acourbot@chromium.org>,
Boris Brezillon <boris.brezillon@collabora.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Ezequiel Garcia <ezequiel@collabora.com>,
Jonas Karlman <jonas@kwiboo.se>
Subject: Re: Proposed updates and guidelines for MPEG-2, H.264 and H.265 stateless support
Date: Tue, 4 Jun 2019 10:55:03 +0200 [thread overview]
Message-ID: <20190604085503.GE9048@ulmo> (raw)
In-Reply-To: <a2f6bac6596da86d597d9ac4c12b1f72b772dbe5.camel@ndufresne.ca>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
On Mon, Jun 03, 2019 at 02:52:44PM -0400, Nicolas Dufresne wrote:
[...]
> There is one thing that come up though, if we enable per-frame decoding
> on top of per-slice decoder (like Cedrus), won't we force userspace to
> always compute l0/l1 even though the HW might be handling that ? Shall
> we instead pass the modification list and implement the non-parsing
> bits of applying the modifications in the kernel ?
Applying the modifications is a standard procedure, right? If it's
completely driver-agnostic, it sounds to me like the right place to
perform the operation is in userspace.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-04 8:55 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 10:09 Proposed updates and guidelines for MPEG-2, H.264 and H.265 stateless support Paul Kocialkowski
2019-05-15 14:42 ` Nicolas Dufresne
2019-05-15 17:42 ` Paul Kocialkowski
2019-05-15 18:54 ` Nicolas Dufresne
2019-05-15 20:59 ` Paul Kocialkowski
2019-05-16 18:24 ` Nicolas Dufresne
2019-05-16 18:45 ` Paul Kocialkowski
2019-05-17 20:43 ` Nicolas Dufresne
2019-05-18 9:50 ` Paul Kocialkowski
2019-05-18 10:04 ` Jernej Škrabec
2019-05-18 10:29 ` Paul Kocialkowski
2019-05-18 14:09 ` Nicolas Dufresne
2019-05-22 6:48 ` Tomasz Figa
2019-05-22 8:26 ` Paul Kocialkowski
2019-05-22 10:42 ` Thierry Reding
2019-05-22 10:55 ` Hans Verkuil
2019-05-22 11:55 ` Thierry Reding
2019-06-07 6:11 ` Tomasz Figa
2019-06-07 6:45 ` Hans Verkuil
2019-06-07 8:23 ` Hans Verkuil
2019-05-21 10:27 ` Tomasz Figa
2019-05-21 11:44 ` Paul Kocialkowski
2019-05-21 15:09 ` Thierry Reding
2019-05-21 16:07 ` Nicolas Dufresne
2019-05-22 8:08 ` Thierry Reding
2019-05-22 6:01 ` Tomasz Figa
2019-05-22 18:15 ` Nicolas Dufresne
2019-05-21 15:43 ` Thierry Reding
2019-05-21 16:23 ` Nicolas Dufresne
2019-05-22 6:39 ` Tomasz Figa
2019-05-22 7:29 ` Boris Brezillon
2019-05-22 8:20 ` Boris Brezillon
2019-05-22 18:18 ` Nicolas Dufresne
2019-05-22 8:32 ` Thierry Reding
2019-05-22 9:29 ` Paul Kocialkowski
2019-05-22 11:39 ` Thierry Reding
2019-05-22 18:31 ` Nicolas Dufresne
2019-05-22 18:26 ` Nicolas Dufresne
2019-05-22 10:08 ` Thierry Reding
2019-05-22 18:37 ` Nicolas Dufresne
2019-05-23 21:04 ` Jonas Karlman
2019-06-03 11:24 ` Thierry Reding
2019-06-03 18:52 ` Nicolas Dufresne
2019-06-03 19:41 ` Boris Brezillon
2019-06-04 8:31 ` Thierry Reding
2019-06-04 8:49 ` Boris Brezillon
2019-06-04 9:06 ` Thierry Reding
2019-06-04 9:15 ` Jonas Karlman
2019-06-04 9:28 ` Paul Kocialkowski
2019-06-04 9:38 ` Boris Brezillon
2019-06-04 10:49 ` Jonas Karlman
2019-06-04 8:50 ` Thierry Reding
2019-06-04 8:55 ` Thierry Reding [this message]
2019-06-04 9:05 ` Boris Brezillon
2019-06-04 9:09 ` Paul Kocialkowski
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=20190604085503.GE9048@ulmo \
--to=thierry.reding@gmail.com \
--cc=acourbot@chromium.org \
--cc=boris.brezillon@collabora.com \
--cc=ezequiel@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=linux-media@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=nicolas@ndufresne.ca \
--cc=paul.kocialkowski@bootlin.com \
--cc=tfiga@chromium.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).