Re: [meta-arago][master/kirkstone][PATCH] conf: arago: Add flag to enable kmssink plugin

[Denys Dmytriyenko <denis@denix.org>]

On Tue, May 23, 2023 at 12:12:01PM +0530, Devarsh Thakkar wrote:
> Hi Denys,
> 
> Thanks for the reply.
> On 23/05/23 04:56, Denys Dmytriyenko wrote:
> > https://patchwork.yoctoproject.org/project/arago/patch/20230522175821.510236-1-b-brnich@ti.com/
> > 
> > If you plan to make major changes to gstreamer or other upstream components, 
> > I'd recommend submitting them upstream to freedesktop. That's the best long 
> > term approach!
> >
> > As meta-ti is a BSP layer, it must avoid heavily modifying generic upstream 
> > components. If there are HW-specific changes necessary, those must be done in 
> > a Yocto Project compliant way - see everything related to Mesa PVR changes 
> > done lately.
> > 
> 
> Upstream looks like a long pole and I suggested this since I see some vendors
> having this in BSP layer [1]
> 
> Although some vendors do that in distro layer too  and using gstreamer fork
> repos [2] as you suggested.
> 
> I am not aware of mesa PVR changes if you/someone could share some reference
> link for the same it would help.
> 
> [1]
> https://git.yoctoproject.org/meta-raspberrypi/tree/recipes-multimedia/gstreamer?h=kirkstone
> 
> [2] https://github.com/Xilinx/meta-petalinux/tree/rel-v2023.1/recipes-multimedia

Well, [1] is a community-driven layer for a vendor platform, but said vendor 
is not at all involved or has any control over it.

Unlike meta-ti, neither [1] nor [2] are certified "Yocto Project Compatible" 
layers, AFAIK.

There are 2 levels of branding and compliance - "Yocto Project Participant" 
and "Yocto Project Compatible" with the latter one requiring more formal 
review and validation process. There are guidelines to follow, and BSP layers 
have the most strict set of rules in order to gain the "Compatible" status - 
meta-ti is among the few of such layers from the very beginning...


> > On Mon, May 22, 2023 at 11:39:31AM +0530, Devarsh Thakkar wrote:
> >> Hi Denys,
> >>
> >> We have a query on location of gstreamer bbappends actually as below :
> >>
> >> As I understand meta-ti is TI's BSP layer and meta-arago is arago distro
> >> layer, if someone want to use TI's BSP with some other distro in place of
> >> arago like poky, then I assume they should be able to take meta-ti and poky
> >> yocto layers. In that case to give them same base, shouldn't the gstreamer
> >> bbappends be present in meta-ti layer itself ?
> >>
> >> Could you please share your opinion on this.
> >>
> >> Regards
> >> Devarsh
> >>
> >> On 18/05/23 23:31, Denys Dmytriyenko wrote:
> >>> On Thu, May 18, 2023 at 06:56:36PM +0530, Rahul T R via lists.yoctoproject.org wrote:
> >>>> Enable building kmssink plugin in gstreamer1.0-plugins-bad
> >>>>
> >>>> Signed-off-by: Rahul T R <r-ravikumar@ti.com>
> >>>> ---
> >>>>  meta-arago-distro/conf/distro/arago.conf | 3 +++
> >>>>  1 file changed, 3 insertions(+)
> >>>>
> >>>> diff --git a/meta-arago-distro/conf/distro/arago.conf b/meta-arago-distro/conf/distro/arago.conf
> >>>> index 379b1d44..e32259a9 100644
> >>>> --- a/meta-arago-distro/conf/distro/arago.conf
> >>>> +++ b/meta-arago-distro/conf/distro/arago.conf
> >>>> @@ -113,6 +113,9 @@ PACKAGECONFIG:append:pn-openssl = " cryptodev-linux"
> >>>>  # Enable GST_TRACER logging in gstreamer
> >>>>  PACKAGECONFIG:append:pn-gstreamer1.0 = " tracer-hooks"
> >>>>  
> >>>> +# Enable kmssink in gstreamer
> >>>> +PACKAGECONFIG:append:pn-gstreamer1.0-plugins-bad = " kms"
> >>>
> >>> FWIW, corresponding bbappend also sets this option, but it needs updating to 
> >>> the current gstreamer version:
> >>>
> >>> https://git.yoctoproject.org/meta-arago/tree/meta-arago-extras/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.16.%25.bbappend#n3
> >>>
> >>>
> >>>>  # Disable pulseaudio routing in alsa by default
> >>>>  PACKAGECONFIG:remove:pn-alsa-plugins = "pulseaudio"
> >>>>  RDEPENDS:pulseaudio-server:remove = "alsa-plugins-pulseaudio-conf"
> >>>> -- 
> >>>> 2.17.1