From: Gary Thomas <gary@mlbassoc.com>
To: Nikolay Dimitrov <picmaster@mail.bg>
Cc: meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm-extra][PATCH v2] riotboard: Fix broken image builds against linux-fslc
Date: Wed, 29 Apr 2015 16:36:54 -0600 [thread overview]
Message-ID: <55415D06.6010506@mlbassoc.com> (raw)
In-Reply-To: <5541575C.4030409@mail.bg>
On 2015-04-29 16:12, Nikolay Dimitrov wrote:
> 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@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.
I'll give it a look and see what I come up with.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2015-04-29 22:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 21:38 [meta-fsl-arm-extra][PATCH v2] riotboard: Fix broken image builds against linux-fslc Nikolay Dimitrov
2015-04-29 21:41 ` Otavio Salvador
2015-04-29 22:46 ` Nikolay Dimitrov
2015-04-29 22:59 ` Fabio Estevam
2015-04-30 2:50 ` Nikolay Dimitrov
2015-04-30 3:22 ` Nikolay Dimitrov
2015-04-30 10:52 ` Otavio Salvador
2015-04-30 14:34 ` Nikolay Dimitrov
2015-04-30 15:13 ` Fabio Estevam
2015-04-30 15:18 ` Nikolay Dimitrov
2015-04-29 21:42 ` Gary Thomas
2015-04-29 21:48 ` Otavio Salvador
2015-04-29 21:55 ` Nikolay Dimitrov
2015-04-29 21:51 ` Nikolay Dimitrov
2015-04-29 21:56 ` Gary Thomas
2015-04-29 22:12 ` Nikolay Dimitrov
2015-04-29 22:36 ` Gary Thomas [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=55415D06.6010506@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
--cc=picmaster@mail.bg \
/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.