mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
To: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
	Bryan O'Donoghue <bod@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Stanimir Varbanov <stanimir.varbanov@linaro.org>,
	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: venus: allow interlaced video streams
Date: Mon, 2 Mar 2026 12:11:14 +0100	[thread overview]
Message-ID: <0884ABDD-8FE6-47CE-A8F4-C5F6061E0FE7@gmail.com> (raw)
In-Reply-To: <885a74d4-c61e-414e-92a1-863faad931ce@oss.qualcomm.com>



> Wiadomość napisana przez Vikash Garodia <vikash.garodia@oss.qualcomm.com> w dniu 2 mar 2026, o godz. 08:31:
> 
> 
> On 3/1/2026 4:05 AM, Dmitry Baryshkov wrote:
>>> 
>>> br
>> Interesting. So, most likely, H.264 decoder can't cope with it and we
>> need to allow non-NONE fields only for MPEG2. Let's see if Vikash will
>> have any other ideas.
> 
> Venus should already support h264 interlace.
> 
> Piotr, do you see the same failure without this patch ?
> 
> Regards,
> Vikash

yes


  reply	other threads:[~2026-03-02 11:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28  9:49 Dmitry Baryshkov
2026-02-28 20:54 ` Piotr Oniszczuk
2026-02-28 22:35   ` Dmitry Baryshkov
2026-03-02  7:31     ` Vikash Garodia
2026-03-02 11:11       ` Piotr Oniszczuk [this message]
2026-03-02 11:28       ` Dmitry Baryshkov
2026-03-04 13:28         ` Vikash Garodia
2026-03-06 11:04           ` Piotr Oniszczuk
2026-08-15 17:55             ` Dmitry Baryshkov

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=0884ABDD-8FE6-47CE-A8F4-C5F6061E0FE7@gmail.com \
    --to=piotr.oniszczuk@gmail.com \
    --cc=bod@kernel.org \
    --cc=dikshita.agarwal@oss.qualcomm.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=stanimir.varbanov@linaro.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
all inboxes | Powered by JetHome®