From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Samuel Holland <samuel@sholland.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Chen-Yu Tsai <wenst@chromium.org>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
linux-media@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Nicolas Dufresne <nicolas.dufresne@collabora.com>
Subject: Re: [PATCH] media: cedrus: Convert to MPLANE uAPI
Date: Mon, 05 Dec 2022 22:01:14 +0100 [thread overview]
Message-ID: <45143854.fMDQidcC6G@kista> (raw)
In-Reply-To: <20221129074530.640251-1-wenst@chromium.org>
Hi Chen-Yu!
Dne torek, 29. november 2022 ob 08:45:30 CET je Chen-Yu Tsai napisal(a):
> The majority of the V4L2 stateless video decoder drivers use the MPLANE
> interface.
>
> On the userspace side, Gstreamer supports non-MPLANE and MPLANE
> interfaces. Chromium only supports the MPLANE interface, and is not yet
> usable with standard desktop Linux. FFmpeg support for either has not
> landed.
I don't like fixing userspace issues in kernel, if kernel side works fine.
Implementing missing non-MPLANE support in Chromium will also allow it to work
with older kernels.
Hans, what's linux-media politics about such changes?
Best regards,
Jernej
>
> A fallback route using libv4l is also available. The library translates
> MPLANE interface ioctl calls to non-MPLANE ones, provided that the pixel
> format used is single plane.
>
> Convert the Cedrus driver to the MPLANE interface, while keeping the
> supported formats single plane. Besides backward compatibility through
> the plugin, the hardware requires that different planes not be located
> too far apart in memory. Keeping the single plane pixel format makes
> this easy to enforce.
>
> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
> ---
>
> This has been tested with Fluster. The score remained the same with or
> without the patch. This also helps with getting VP8 decoding working
> with Chromium's in-tree test program "video_decode_accelerator_tests",
> though Chromium requires other changes regarding buffer allocation and
> management.
next prev parent reply other threads:[~2022-12-05 21:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 7:45 [PATCH] media: cedrus: Convert to MPLANE uAPI Chen-Yu Tsai
2022-12-05 21:01 ` Jernej Škrabec [this message]
2022-12-06 8:34 ` Hans Verkuil
2022-12-06 12:23 ` Chen-Yu Tsai
2022-12-06 19:15 ` Nicolas Dufresne
2022-12-07 8:05 ` Hans Verkuil
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=45143854.fMDQidcC6G@kista \
--to=jernej.skrabec@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=samuel@sholland.org \
--cc=wenst@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