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: Fri, 6 Mar 2026 12:04:28 +0100 [thread overview]
Message-ID: <D3656655-844F-4369-97FF-0A57D023E988@gmail.com> (raw)
In-Reply-To: <d3310437-2776-4c7f-a844-8dc5de0f6359@oss.qualcomm.com>
> Wiadomość napisana przez Vikash Garodia <vikash.garodia@oss.qualcomm.com> w dniu 4 mar 2026, o godz. 14:28:
>
>
>>>>
>>>> have any other ideas.
>>>>
>>>
>>> Venus should already support h264 interlace.
>> I guess, the question is: do we support interlaced H.264 streams?
>
> Yes, we do support interlace.
>
Hmm - i'm curious: when you are saying "we do support " - it this mean:
1. just support or,
2. suport for demonstrating working state or,
3. support for useful usage (i mean useful in user space like e.g media players)
Isn't target to have option3?
I have qcs6490 and decoder fails on:
-kodi
-mythtv
-mpv
Tested only on 3 major players as i'm afraid other exotic userspace is rather niche for users...
And believe me - repaying to mine users: "hey - my distro supports video decoder on qcs6490 as i can prove it by showing you working test tools on it" is not what they want to see.
next prev parent reply other threads:[~2026-03-06 11:04 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
2026-03-02 11:28 ` Dmitry Baryshkov
2026-03-04 13:28 ` Vikash Garodia
2026-03-06 11:04 ` Piotr Oniszczuk [this message]
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=D3656655-844F-4369-97FF-0A57D023E988@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®