From: Dragan Simic <dsimic@manjaro.org>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: "Piotr Oniszczuk" <piotr.oniszczuk@gmail.com>,
"Andy Yan" <andy.yan@rock-chips.com>,
陈恒明 <herman.chen@rock-chips.com>,
Linux-rockchip@lists.infradead.org
Subject: Re: vop2: 3566 vs 3568: green screen on 3566; on 3568 all ok...
Date: Wed, 27 Dec 2023 08:36:41 +0100 [thread overview]
Message-ID: <fb43b99af44308232700dbf30e313cd0@manjaro.org> (raw)
In-Reply-To: <a9dd13e5-6433-4509-b4b7-61c50fbca8dd@rock-chips.com>
On 2023-12-27 08:25, Kever Yang wrote:
> On 2023/12/26 19:22, Piotr Oniszczuk wrote:
> ...
>> Perfect.
>>
>> Above patch + vop2_win_data rk3568_vop_win_data[] reordering to:
>>
>> Esmart1-win0
>> Esmart0-win0
>> Smart0-win0
>> Smart1-win0
>> Cluster0-win0
>> Cluster1-win0
>>
>> makes Kodi and MythTV working out-of-box with EGL DMAbuf and DRM
>> planes HW decoded video rendering :-)
>>
>> So with your help we have single 6.6.8 kernel offering EGL DMAbuf and
>> DRM planes HW decoded video rendering on
>> rk3328/rk3399/rk3566/rk3568/H6/H313/H616/H618/rpi3/rpi4
>>
>> once again: many thx
>>
>> (p.s: it looks like only thing missing in 356x to be perfect
>> open-source multimedia soc is: lack of rkvdec2 for hevc/vp9 hw
>> decoding. Are there any plans from rock-chips to help foss to bring-up
>> mainline kernel support for rkvdec2?)
>
> Rockchip do not have plan to add rkvdec2 driver for mainline kernel,
> since rockchip vendor SDK does not use V4L2 based solution for video
> encoder/decoder.
> For rkvdec, rockchip has already totally open source for both kernel
> driver and userspace mpp driver, people can understand how it works if
> anyone interested in it.
This is awesome. Though, could you, please, send the links to the
actual official source code repositories, simply because there seems to
be quite a few of such repositories, which becomes confusing rather
quickly?
> If developers would like to port the driver for mainline kernel, it's
> welcome and if you have any questions about the hardware during
> porting the driver, we can help to answer.
This is also awesome, thank you very much.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2023-12-27 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-24 12:37 vop2: 3566 vs 3568: green screen on 3566; on 3568 all ok Piotr Oniszczuk
2023-12-25 1:40 ` Andy Yan
2023-12-25 12:14 ` Piotr Oniszczuk
2023-12-26 1:41 ` Andy Yan
2023-12-26 11:22 ` Piotr Oniszczuk
2023-12-27 7:25 ` Kever Yang
2023-12-27 7:36 ` Dragan Simic [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=fb43b99af44308232700dbf30e313cd0@manjaro.org \
--to=dsimic@manjaro.org \
--cc=Linux-rockchip@lists.infradead.org \
--cc=andy.yan@rock-chips.com \
--cc=herman.chen@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=piotr.oniszczuk@gmail.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