From: Dmitry Osipenko <digetx@gmail.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Vladimir Zapolskiy <vz@mleia.com>,
Rob Herring <robh+dt@kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-media <linux-media@vger.kernel.org>,
devel@driverdev.osuosl.org,
devicetree <devicetree@vger.kernel.org>,
linux-tegra@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 2/4] staging: media: Introduce NVIDIA Tegra video decoder driver
Date: Sun, 22 Nov 2020 05:01:09 +0300 [thread overview]
Message-ID: <5665b221-04d7-6be9-2377-8006b9563d4b@gmail.com> (raw)
In-Reply-To: <CAAEAJfBZD0u6MDxcp3See-agzyCSJS7dKpwK28LMJwPvE9DLtQ@mail.gmail.com>
22.11.2020 04:02, Ezequiel Garcia пишет:
> Hi Dmitry,
>
...
>> +++ b/drivers/staging/media/tegra-vde/TODO
>> @@ -0,0 +1,4 @@
>> +TODO:
>> + - Implement V4L2 API once it gains support for stateless decoders.
>> +
>> +Contact: Dmitry Osipenko <digetx@gmail.com>
>
> The API for H264 stateless decoding is ready.
> See https://lkml.org/lkml/2020/11/18/795.
Hello Ezequiel,
Thank you for the notification! My last attempt at implementing V4L API
support was about a year ago and it stopped once I realized that there
is no userspace which uses that API. FFMPEG and chromium browser had
some kind of V4L support, but it all was oriented at downstream driver
stacks, and thus, not usable. Do you know what is the current status?
> One minor comment below.
>
...
>> + // PPS
>> + __u8 pic_init_qp;
>> + __u8 deblocking_filter_control_present_flag;
>> + __u8 constrained_intra_pred_flag;
>> + __u8 chroma_qp_index_offset;
>> + __u8 pic_order_present_flag;
>> +
>
> This seems to be bottom_field_pic_order_in_frame_present_flag,
> as there is no "pic_order_present_flag" syntax element.
Correct, looks like I borrowed that name from the libvdpau API.
https://vdpau.pages.freedesktop.org/libvdpau/struct_vdp_picture_info_h264.html#a405f7ef26ea76bb2c446e151062fc001
next prev parent reply other threads:[~2020-11-22 2:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 0:26 [PATCH v5 0/4] " Dmitry Osipenko
2017-12-12 0:26 ` [PATCH v5 1/4] media: dt: bindings: Add binding for NVIDIA Tegra Video Decoder Engine Dmitry Osipenko
2017-12-12 0:26 ` [PATCH v5 2/4] staging: media: Introduce NVIDIA Tegra video decoder driver Dmitry Osipenko
2020-11-22 1:02 ` Ezequiel Garcia
2020-11-22 2:01 ` Dmitry Osipenko [this message]
2020-11-23 3:07 ` Ezequiel Garcia
2020-11-23 11:09 ` Dmitry Osipenko
2017-12-12 0:26 ` [PATCH v5 3/4] ARM: dts: tegra20: Add device tree node to describe IRAM Dmitry Osipenko
2017-12-20 19:19 ` Thierry Reding
2017-12-12 0:26 ` [PATCH v5 4/4] ARM: dts: tegra20: Add video decoder node Dmitry Osipenko
2017-12-20 19:19 ` Thierry Reding
2017-12-17 18:03 ` [PATCH v5 0/4] NVIDIA Tegra video decoder driver Dmitry Osipenko
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=5665b221-04d7-6be9-2377-8006b9563d4b@gmail.com \
--to=digetx@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=vz@mleia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®