From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Zhentao Guo <zhentao.guo@amlogic.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 0/3] Add Amlogic stateless H.264 video decoder for S4
Date: Tue, 04 Nov 2025 11:13:01 -0500 [thread overview]
Message-ID: <b6e6881197dc4c83e43ef5eb1f20c2bf1887d395.camel@ndufresne.ca> (raw)
In-Reply-To: <540d98ea-114c-43bc-94c0-e944b5613d74@amlogic.com>
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Hi,
Le mardi 28 octobre 2025 à 19:47 +0800, Zhentao Guo a écrit :
> Ran 54/135 tests successfully
>
> - 52 test vectors failed due to interlaced or mbaff clips: The Amlogic
> stateless
> decoder driver only support bitstreams with frame_mbs_only_flags == 1.
> Test Vectors:
Is there plan to support it ? Most of the legacy content, and why users wants
H.264 around is to handle interlaced content. Its also not really optional in
the ITU conformance spec.
regards,
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-04 16:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 5:42 [PATCH 0/3] Add Amlogic stateless H.264 video decoder for S4 Zhentao Guo via B4 Relay
2025-10-27 5:42 ` [PATCH 1/3] dt-bindings: vdec: Add binding document of Amlogic decoder accelerator Zhentao Guo via B4 Relay
2025-10-27 13:05 ` Krzysztof Kozlowski
2025-10-28 11:14 ` Zhentao Guo
2025-10-28 11:33 ` Krzysztof Kozlowski
2025-10-28 12:23 ` Zhentao Guo
2025-10-27 5:42 ` [PATCH 2/3] dts: decoder: Support V4L2 stateless decoder dt node for S4 Zhentao Guo via B4 Relay
2025-10-27 13:06 ` Krzysztof Kozlowski
2025-10-28 11:18 ` Zhentao Guo
2025-10-27 5:42 ` [PATCH 3/3] decoder: Add V4L2 stateless H.264 decoder driver Zhentao Guo via B4 Relay
2025-10-27 13:10 ` Krzysztof Kozlowski
2025-10-28 11:22 ` Zhentao Guo
2025-10-28 11:01 ` Neil Armstrong
2025-10-28 12:16 ` Zhentao Guo
2025-11-08 22:53 ` Martin Blumenstingl
2025-11-10 4:05 ` Zhentao Guo
2025-10-27 12:57 ` [PATCH 0/3] Add Amlogic stateless H.264 video decoder for S4 Christian Hewitt
2025-10-28 11:08 ` Zhentao Guo
2025-10-30 10:50 ` Ferass El Hafidi
2025-10-31 2:32 ` Zhentao Guo
2025-10-28 10:50 ` Neil Armstrong
2025-10-28 11:47 ` Zhentao Guo
2025-11-04 7:28 ` Christian Hewitt
2025-11-04 16:13 ` Nicolas Dufresne [this message]
2025-11-05 9:26 ` Zhentao Guo
2025-11-05 13:51 ` Nicolas Dufresne
2025-11-06 2:44 ` Zhentao Guo
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=b6e6881197dc4c83e43ef5eb1f20c2bf1887d395.camel@ndufresne.ca \
--to=nicolas@ndufresne.ca \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mchehab@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=zhentao.guo@amlogic.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;
as well as URLs for NNTP newsgroup(s).