From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
"Hans Verkuil" <hverkuil@xs4all.nl>,
"Sakari Ailus" <sakari.ailus@iki.fi>,
"Andrzej Pietrasiewicz" <andrzej.p@collabora.com>,
"Michael Tretter" <m.tretter@pengutronix.de>,
"Jernej Škrabec" <jernej.skrabec@gmail.com>,
"Chen-Yu Tsai" <wens@csie.org>,
"Samuel Holland" <samuel@sholland.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: Stateless Encoding uAPI Discussion and Proposal
Date: Wed, 15 Nov 2023 14:19:12 +0100 [thread overview]
Message-ID: <ZVTFUKPxKvcBjg95@aptenodytes> (raw)
In-Reply-To: <ZOW91rIXS8fTWZ6I@aptenodytes>
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
Hi folks,
Just a quick message on this thread to let you know that we have just published
the code for the H.264 encoding extension to cedrus for the V3/V3s/S3.
You can find more details in the dedicated blog post:
- https://bootlin.com/blog/open-source-linux-kernel-support-for-the-allwinner-v3-v3s-s3-h-264-video-encoder/
And the code is at:
- https://github.com/bootlin/linux/tree/cedrus/h264-encoding
- https://github.com/bootlin/v4l2-cedrus-enc-test
As announced this doesn't really help advance our uAPI discussion here since
there is no rate-control yet and the stateful controls are reused for
controlling the encoding features (including things like GOP).
Cheers,
Paul
--
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-11-15 13:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 17:12 Stateless Encoding uAPI Discussion and Proposal Paul Kocialkowski
2023-07-11 18:18 ` Nicolas Dufresne
2023-07-12 14:07 ` Paul Kocialkowski
2023-07-25 3:33 ` Hsia-Jun Li
2023-07-25 12:15 ` Paul Kocialkowski
2023-07-26 2:49 ` Hsia-Jun Li
2023-07-26 19:53 ` Nicolas Dufresne
2023-07-27 2:45 ` Hsia-Jun Li
2023-07-27 17:10 ` Nicolas Dufresne
2023-07-26 8:18 ` Hans Verkuil
2023-08-09 14:43 ` Paul Kocialkowski
2023-08-09 17:24 ` Andrzej Pietrasiewicz
2023-07-21 18:19 ` Michael Grzeschik
2023-07-24 14:03 ` Nicolas Dufresne
2023-07-25 9:09 ` Paul Kocialkowski
2023-07-26 20:02 ` Nicolas Dufresne
2023-08-10 13:44 ` Paul Kocialkowski
2023-08-10 14:34 ` Nicolas Dufresne
2023-08-11 20:08 ` Paul Kocialkowski
2023-08-21 15:13 ` Nicolas Dufresne
2023-08-22 8:30 ` Hsia-Jun Li
2023-08-22 20:31 ` Nicolas Dufresne
2023-08-23 3:04 ` Hsia-Jun Li
2023-08-30 15:10 ` Nicolas Dufresne
2023-08-30 16:51 ` Randy Li
2023-08-30 15:18 ` Nicolas Dufresne
2023-08-31 9:32 ` Hsia-Jun Li
2023-08-23 8:05 ` Paul Kocialkowski
2023-11-15 13:19 ` Paul Kocialkowski [this message]
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=ZVTFUKPxKvcBjg95@aptenodytes \
--to=paul.kocialkowski@bootlin.com \
--cc=andrzej.p@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=jernej.skrabec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=nicolas.dufresne@collabora.com \
--cc=sakari.ailus@iki.fi \
--cc=samuel@sholland.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).