All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Gary Thomas <gary@mlbassoc.com>
Subject: Re: [meta-fsl-arm-extra][PATCH v2] riotboard: Fix broken image builds against linux-fslc
Date: Thu, 30 Apr 2015 00:55:23 +0300	[thread overview]
Message-ID: <5541534B.5050000@mail.bg> (raw)
In-Reply-To: <CAP9ODKpdXfakk=CFZ8O+FC=4JHgBor0eZ7RgrmpBGDhZyp8ZwA@mail.gmail.com>

Hi Otavio,

On 04/30/2015 12:48 AM, Otavio Salvador wrote:
> On Wed, Apr 29, 2015 at 6:42 PM, Gary Thomas <gary@mlbassoc.com> 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.
>
> When he does this the forked 3.14 kernel will likely to become the
> default one and those can be removed.

Not exactly. We're doing work to enable Yocto to work with linux-fslc,
and it would be unfair to throw this work on the junk. I would prefer
to see both mainline and fsl kernels being able to be used in a Yocto
build.

> When I have some free time I will try to come up with a generic way to
> 'inform' the BSP about the kernel features and avoid those hacks.

This would be very welcome for cases like this. Thanks in advance for
helping out.

Regards,
Nikolay


  reply	other threads:[~2015-04-29 21:55 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 [this message]
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

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=5541534B.5050000@mail.bg \
    --to=picmaster@mail.bg \
    --cc=gary@mlbassoc.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.