From: Trevor Woerner <twoerner@gmail.com>
To: yocto-patches@lists.yoctoproject.org
Cc: Quentin Schulz <foss+yocto@0leil.net>
Subject: Re: [yocto-patches] [meta-rockchip PATCH 3/9] rk3399: enable gstreamer v4l2codecs support
Date: Wed, 21 Aug 2024 00:42:43 -0400 [thread overview]
Message-ID: <20240821044243.GA1194@localhost> (raw)
In-Reply-To: <b6d2f95b-ebb8-436a-8644-fb63f8126c56@cherry.de>
On Tue 2024-08-20 @ 03:48:16 PM, Quentin Schulz via lists.yoctoproject.org wrote:
>
>
> On 8/20/24 2:56 PM, Quentin Schulz wrote:
> > From: Quentin Schulz <quentin.schulz@cherry.de>
> >
> > RK3399 has a Hantro VPU, so let's set HAS_HANTRO so that gstreamer
> > v4l2codecs plugin can be built.
> >
>
> RK3399 actually also has an RKVDEC VPU which is used for decoding H.264, VP9
> and H.265. Currently, rkvdec supports H.264 and VP9 decoding, while Hantro
> supports VP8 and MPEG2 decoding as well as JPEG encoding. Therefore, I'm not
> sure the naming of the variable is proper? Should we go for
> HAS_STATELESS_VPU instead?
What about 2 knobs:
1. HAS_HANTRO
2. HAS_RKVDEC
?
Does gstreamer have knobs for both sets?
> Cheers,
> Quentin
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#535): https://lists.yoctoproject.org/g/yocto-patches/message/535
> Mute This Topic: https://lists.yoctoproject.org/mt/107999800/900817
> Group Owner: yocto-patches+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto-patches/leave/13168745/900817/63955952/xyzzy [twoerner@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
next prev parent reply other threads:[~2024-08-21 4:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 12:56 [meta-rockchip PATCH 0/9] enable v4l2codecs gstreamer plugin for VPU decoding Quentin Schulz
2024-08-20 12:56 ` [meta-rockchip PATCH 1/9] gstreamer-plugins-bad: build v4l2codecs if SoC has a VPU Quentin Schulz
2024-08-20 12:56 ` [meta-rockchip PATCH 2/9] px30: enable gstreamer v4l2codecs support Quentin Schulz
2024-08-20 12:56 ` [meta-rockchip PATCH 3/9] rk3399: " Quentin Schulz
2024-08-20 13:48 ` Quentin Schulz
2024-08-21 4:42 ` Trevor Woerner [this message]
2024-08-21 8:17 ` [yocto-patches] " Quentin Schulz
2024-08-22 12:23 ` Trevor Woerner
2024-08-22 12:38 ` Quentin Schulz
2024-08-23 13:55 ` Trevor Woerner
2024-08-26 15:35 ` Quentin Schulz
2024-08-27 15:10 ` Trevor Woerner
2024-08-27 15:12 ` Quentin Schulz
2024-08-20 12:56 ` [meta-rockchip PATCH 4/9] rk3066: " Quentin Schulz
2024-08-20 12:56 ` [meta-rockchip PATCH 5/9] rk3188: " Quentin Schulz
2024-08-20 12:56 ` [meta-rockchip PATCH 6/9] rk3288: " Quentin Schulz
2024-08-20 12:56 ` [meta-rockchip PATCH 7/9] rk3328: " Quentin Schulz
2024-08-20 12:56 ` [meta-rockchip PATCH 8/9] rk356x: " Quentin Schulz
2024-08-20 12:56 ` [meta-rockchip PATCH 9/9] rk3588(s): " Quentin Schulz
2024-08-20 13:24 ` [meta-rockchip PATCH 0/9] enable v4l2codecs gstreamer plugin for VPU decoding Quentin Schulz
2024-08-21 15:34 ` Quentin Schulz
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=20240821044243.GA1194@localhost \
--to=twoerner@gmail.com \
--cc=foss+yocto@0leil.net \
--cc=yocto-patches@lists.yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.