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>
Subject: Re: [meta-fsl-demos][PATCH] riotboard: Fix broken image builds against linux-fslc
Date: Tue, 12 May 2015 02:42:50 +0300	[thread overview]
Message-ID: <55513E7A.4060304@mail.bg> (raw)
In-Reply-To: <CAP9ODKoug2fVSNs5narNCh2K+_ixeOtH56pMiJ1f71L3Ho9qFQ@mail.gmail.com>

Hi Otavio,

On 05/11/2015 08:46 PM, Otavio Salvador wrote:
> On Mon, May 11, 2015 at 2:24 PM, Nikolay Dimitrov <picmaster@mail.bg>
> wrote:
>> Hi Otavio,
>>
>> On 05/11/2015 08:09 PM, Otavio Salvador wrote:
>>>
>>> On Mon, May 11, 2015 at 1:43 PM, Nikolay Dimitrov
>>> <picmaster@mail.bg> wrote:
>>>>
>>>> Ping.
>>>
>>>
>>> I am building it here for testing.
>>
>>
>> That's great, thanks for looking into it.
>
> Your patch can get a change:
>
> diff --git a/conf/machine/imx6dl-riotboard.conf
> b/conf/machine/imx6dl-riotboard.conf index bf50eaf..260deed 100644
> --- a/conf/machine/imx6dl-riotboard.conf +++
> b/conf/machine/imx6dl-riotboard.conf @@ -19,4 +19,4 @@ SERIAL_CONSOLE
> = "115200 ttymxc1" # FIXME: Workaround for building against
> linux-fslc MACHINE_EXTRA_RRECOMMENDS_remove = "fsl-alsa-plugins"
> PREFERRED_VERSION_imx-test = "00.00.00" -MACHINE_GSTREAMER_PLUGIN =
> "" +MACHINE_GSTREAMER_PLUGIN_imx6dl-riotboard = ""
>
> This makes the patch in meta-fsl-demos not needed and seems cleaner.
>
> Can you take a look and confirm?

This code sits in riotboard-specific conf file, so there's no difference
between MACHINE_GSTREAMER_PLUGIN and
MACHINE_GSTREAMER_PLUGIN_imx6dl-riotboard variables. The machine suffix
is redundant in the 2nd case. But even if I use the proposed
MACHINE_GSTREAMER_PLUGIN_imx6dl-riotboard, the fsl-image-multimedia-full
image build still fails.

Regarding the meta-fsl-demos patch - the need for this fix is because
the packagegroup-fsl-gstreamer-full.bb is again adding the
gst-plugins-gl dependency, disregarding the available capabilities
(either hardware or kernel).

So, my motivation for doing it this way for short term is the following:
1. I still have single kernel to maintain (fslc) as of today.
2. The board builds are broken at least since 23.April and I have to do
something about it.

FYI, for a long-term solution I plan to do the following, if you agree:
- Support building multiple kernels, including both FSL and FSLC
- Somehow declare the capabilities of the hardware/kernel and take it
into account by in recipes. We need something like KERNEL_FEATURES and
MACHINE_FEATURES, and only if a feature is declared by both variables,
then it should be used (not sure whether this is the same as the
COMBINED_FEATURES mechanism). I'm looking towards your ideas here, as
you guys have much more Yocto experience than me.

To summarize: my patch set is not perfect, but as of today we don't
have all the ingredients to make it perfect. Tomorrow we could have
these ingredients, but I can't see how far is this tomorrow.

Regards,
Nikolay


  reply	other threads:[~2015-05-11 23:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 15:49 [meta-fsl-arm-extra][PATCH v3] riotboard: Fix broken image builds against linux-fslc Nikolay Dimitrov
2015-04-30 15:49 ` [meta-fsl-demos][PATCH] " Nikolay Dimitrov
2015-05-04 12:41   ` Fabio Estevam
2015-05-04 13:33     ` Nikolay Dimitrov
2015-05-04 17:06       ` Daiane Angolini
2015-05-04 17:12         ` Gary Thomas
2015-05-04 19:38         ` Nikolay Dimitrov
2015-05-11 16:43   ` Nikolay Dimitrov
2015-05-11 17:09     ` Otavio Salvador
2015-05-11 17:24       ` Nikolay Dimitrov
2015-05-11 17:46         ` Otavio Salvador
2015-05-11 23:42           ` Nikolay Dimitrov [this message]
2015-05-12 12:41             ` Otavio Salvador
2015-05-13  4:09               ` Nikolay Dimitrov
2015-05-13 11:06                 ` Otavio Salvador
2015-05-11 16:42 ` [meta-fsl-arm-extra][PATCH v3] " Nikolay Dimitrov

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=55513E7A.4060304@mail.bg \
    --to=picmaster@mail.bg \
    --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.