From: Bryan O'Donoghue <bod@kernel.org>
To: Christian Cortner <ccortner@gmail.com>,
Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
Cc: Abhinav Kumar <abhinav.kumar@linux.dev>,
Birk Skyum <birk.skyum@pm.me>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [BUG] media: iris: resolution change handling stops ffmpeg's h264_v4l2m2m decoder on glymur
Date: Mon, 26 Oct 2026 22:31:26 +0000 [thread overview]
Message-ID: <36201ae2-1cee-4d8d-9381-dfc9013c522e@kernel.org> (raw)
In-Reply-To: <20261026160952.22082-1-ccortner@gmail.com>
On 26/10/2026 16:09, Christian Cortner wrote:
> Hi,
>
> On an ASUS Zenbook A16 (UX3607OA, Snapdragon X2 Elite / glymur),
> ffmpeg's h264_v4l2m2m decoder outputs one corrupted frame and stops,
> on every stream I tried. GStreamer's V4L2 decoders work. Below are the
> two driver behaviours behind it (1 and 2), two more that stop ffmpeg
> at a resolution change in the middle of a stream (3 and 4), and an
> inconsistent CAPTURE format that ffmpeg happens to avoid (5).
>
> I'm not a kernel developer. I tracked this down with an AI coding
> assistant (Claude, by Anthropic): it traced the driver, wrote a small
> V4L2 test client and tried changes to the driver. Everything below was
> run on this laptop, and each local change described made its problem
> go away here. I can't review or defend kernel patches myself, so I'm
> reporting the problems instead of sending fixes, but I'm glad to test
> patches on this machine.
Err thanks for the bug report but, if you have a test-case and a
resolution - even of the code sucks and/or you don't understand it,
please post the code.
One of us can take up the task of finishing it off.
After all we are burning down the rainforest for this stuff so no sense
in wasting the already spent compute time and power.
---
bod
next prev parent reply other threads:[~2026-10-26 22:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NKVWOXEaC2RjmCRG3wt6Y-1_CZxSqp_rpkiLIJV8xQg9k4sZGi5C2lZ4oIQ0qsI-Fk-wDDfmYsiCOiqKaDFnzQ==@protonmail.internalid>
2026-10-26 16:09 ` [BUG] media: iris: resolution change handling stops ffmpeg's h264_v4l2m2m decoder on glymur Christian Cortner
2026-10-26 17:50 ` Birk Skyum
2026-10-26 21:13 ` Birk Skyum
2026-10-26 22:31 ` Bryan O'Donoghue [this message]
2026-10-27 2:19 ` Christian Cortner
2026-10-27 2:19 ` [RFC PATCH 0/5] media: iris: ffmpeg decoder flow changes, for reference only Christian Cortner
2026-10-27 2:19 ` [RFC PATCH 1/5] media: iris: Don't flag an empty source change LAST buffer as an error Christian Cortner
2026-10-27 22:26 ` Bryan O'Donoghue
2026-10-27 2:19 ` [RFC PATCH 2/5] media: iris: Update the CAPTURE stride and size on S_FMT(OUTPUT) Christian Cortner
2026-10-27 22:36 ` Bryan O'Donoghue
2026-10-27 2:19 ` [RFC PATCH 3/5] media: iris: Signal V4L2_EVENT_EOS only at the end of a drain Christian Cortner
2026-10-27 22:44 ` Bryan O'Donoghue
2026-10-27 2:19 ` [RFC PATCH 4/5] media: iris: Let a resolution change drain before stopping CAPTURE Christian Cortner
2026-10-27 22:59 ` Bryan O'Donoghue
2026-10-27 2:19 ` [RFC PATCH 5/5] media: iris: Resume the first source change if it fits the CAPTURE setup Christian Cortner
2026-10-27 23:04 ` Bryan O'Donoghue
2026-10-27 12:43 ` [BUG] media: iris: resolution change handling stops ffmpeg's h264_v4l2m2m decoder on glymur Birk Skyum
2026-10-27 18:14 ` Christian Cortner
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=36201ae2-1cee-4d8d-9381-dfc9013c522e@kernel.org \
--to=bod@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=birk.skyum@pm.me \
--cc=ccortner@gmail.com \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=vikash.garodia@oss.qualcomm.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