[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1512934179.4281.15.camel@ndufresne.ca>
Date: Sun, 10 Dec 2017 14:29:39 -0500
From: Nicolas Dufresne <nicolas@...fresne.ca>
To: Dmitry Osipenko <digetx@...il.com>,
Hans Verkuil <hverkuil@...all.nl>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh+dt@...nel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Stephen Warren <swarren@...dotorg.org>,
Vladimir Zapolskiy <vz@...ia.com>
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
linux-media@...r.kernel.org, linux-tegra@...r.kernel.org,
devel@...verdev.osuosl.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Giulio Benetti <giulio.benetti@...ronovasrl.com>
Subject: Re: [PATCH v4 3/5] staging: Introduce NVIDIA Tegra video decoder
driver
Le dimanche 10 décembre 2017 à 21:56 +0300, Dmitry Osipenko a écrit :
> > I've CC-ed Maxime and Giulio as well: they are looking into adding support for
> > the stateless allwinner codec based on this code as well. There may well be
> > opportunities for you to work together, esp. on the userspace side. Note that
> > Rockchip has the same issue, they too have a stateless HW codec.
>
> IIUC, we will have to define video decoder parameters in V4L API and then make a
> V4L driver / userspace prototype (ffmpeg for example) that will use the requests
> API for video decoding in order to upstream the requests API. Does it sound good?
Chromium/Chrome already have support for that type of decoder in their
tree. In theory, it should just work.
Nicolas
Powered by blists - more mailing lists