[meta-freescale] [meta-fsl-arm-extra][PATCH v2] riotboard: Fix broken image builds against linux-fslc

[Nikolay Dimitrov]

Hi Gary,

On 04/30/2015 12:56 AM, Gary Thomas wrote:
> On 2015-04-29 15:51, Nikolay Dimitrov wrote:
>> Hi Gary,
>>
>> On 04/30/2015 12:42 AM, Gary Thomas wrote:
>>> On 2015-04-29 15:38, Nikolay Dimitrov wrote:
>>>> Several Yocto images fail to build because they're using packages that
>>>> require
>>>> imx6-specific hardware support (ASRC, VPU, GPU3D), which is not
>>>> available in
>>>> the mainline kernel. This patch fixes the following image builds:
>>>> - core-image-minimal
>>>> - core-image-base
>>>> - fsl-image-multimedia
>>>>
>>>> Signed-off-by: Nikolay Dimitrov <picmaster at mail.bg>
>>>> ---
>>>>   conf/machine/imx6dl-riotboard.conf |    3 +++
>>>>   1 file changed, 3 insertions(+)
>>>>
>>>> diff --git a/conf/machine/imx6dl-riotboard.conf
>>>> b/conf/machine/imx6dl-riotboard.conf
>>>> index b611ffb..05f6a38 100644
>>>> --- a/conf/machine/imx6dl-riotboard.conf
>>>> +++ b/conf/machine/imx6dl-riotboard.conf
>>>> @@ -15,3 +15,6 @@ PREFERRED_PROVIDER_virtual/kernel ?= "linux-fslc"
>>>>   KERNEL_DEVICETREE = "imx6dl-riotboard.dtb"
>>>>
>>>>   SERIAL_CONSOLE = "115200 ttymxc1"
>>>> +
>>>> +MACHINE_EXTRA_RRECOMMENDS_remove = "fsl-alsa-plugins"
>>>> +MACHINE_GSTREAMER_PLUGIN_imx6dl-riotboard = ""
>>>>
>>>
>>> Is there some way to make this weaker?  For example, these
>>> changes will be icorrect if [when?] you get the linux-fslc 3.14
>>> kernel going.
>>
>> Yes, I was also thinking about it. My plan is to fix this when
>> introducing the 3.14 support, but as of today there's no such support
>> for riotboard, so I would prefer to push whatever I have
>> working.
>
> I've not looked at backporting to 3.14 (I was leaving that for you!)
> but how different would the device tree from 4.1-rc1 need to be to
> work with 3.14?  Isn't that (plus the stitching to get it built)
> about all that's needed?

I don't expect any back-porting work for FSL 3.14.28 kernel, only DT
work. My last experience of playing with DTs on several imx6 dual/quad
customer boards showed that beyond the initial enthusiasm it always
took much more than initially estimated, sometimes up to 2-3 days work.

I don't like to say that, but for most of us Yocto is a spare-time
effort, which means its priority is below the commercial projects we're
working on. But I can assure you that I would love to see 3.14.28
running on riotboard, just as you, and I'll do my best to make it
happen.

If you feel enthusiastic about helping out with enabling the 3.14.28
kernel support, your help will be warmly appreciated.

Regards,
Nikolay