[yocto] [meta-rockchip] [PATCH v2 3/3] recipes-multimedia: images: rockchip media image

[Andre McCurdy]

 On Mon, May 15, 2017 at 10:23 AM, Khem Raj <raj.khem at gmail.com> wrote:
> On Mon, May 15, 2017 at 9:33 AM, Trevor Woerner <twoerner at gmail.com> wrote:
>> On Sat 2017-05-13 @ 06:20:35 PM, Romain Perier wrote:
>>> Clearly a NAK here. I don't want yet another image for this, that's a
>>> bsp meta layer, it is supposed to contain the recipes and rules to
>>> propose support for Rockchip SocS in in yocto/oe and its reference
>>> distros. But it is also supposed to be minimal, I don't want "all the
>>> world"  in meta-rockchip, to be honest :)
>>>
>>> I am not fan to have recipes or rules for development...
>>>
>>> Trevor, as a co-maintainer, what is your point about this ? (always welcome)
>>
>> It's not uncommon for BSP layers to include sample image recipes
>> (meta-raspberrypi, for example, includes rpi-test-image, rpi-basic-image, and
>> rpi-hwup-image). These sample images act as a sort of example, or
>> documentation for others to follow. They're a way to show off what can be
>> done.
>>
>> This recipe could act as an example should anyone want to integrate gstreamer
>> support for a rockchip in their image (assuming this image builds and works).
>
> you could also make a packagegroup and leave it there and let end user to
> include the packagegroup in his/her image

It looks like the COMMERCIAL_AUDIO_PLUGINS and
COMMERCIAL_VIDEO_PLUGINS hooks could be used to add machine specific
plugins to the existing gstreamer1.0-meta-audio and
gstreamer1.0-meta-video package groups?

>>
>> I'm not opposed to it being there, as long as it's benign and works.
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto