All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: oe-core layer including support for i.MX28
Date: Thu, 15 Mar 2012 17:26:42 +0000	[thread overview]
Message-ID: <4F622652.30001@dynamicdevices.co.uk> (raw)
In-Reply-To: <CAP9ODKqUQAkn9B_rTiG2usVvD+4=U9arufuK3fNfy5ieB2y82Q@mail.gmail.com>


>That said, I do believe you ought to check if your changes cannot be made generic

Will try to keep in mind.

>Please complain at them ... this is the only way to revert it.

I'll keep on at them :) Anything not to have to go back to LTIB... ;)

Alex

On 15/03/2012 17:21, Otavio Salvador wrote:
> On Thu, Mar 15, 2012 at 14:16, Alex J Lennon
> <ajlennon@dynamicdevices.co.uk>  wrote:
>>> I think the first solution is better and that custom boards should be added
>>> to custom layers
>> Hmmm ok, thanks That being the case it may be better for me to migrate my
>> recipes from
>> the oe-classic codebase into a new layer created from scratch. It'll be
>> quicker and easier for
>> me that way but perhaps less generic.
> I think many things can be merged back but it is better to have custom
> boards in specific layers that inherit meta-fsl-arm. That said, I do
> believe you ought to check if your changes cannot be made generic
> (ofthenly it can be done) and this could allow it to be merged here.
>
>> (Although my understanding was that Freescale have no intention of providing
>> Linux support related
>>   to OpenEmbedded at this time? Or at least that's what they are telling me
>> :)
> Please complain at them ... this is the only way to revert it. Some
> individuals are working with OpenEmbedded/Yocto and it might end
> changing the Freescale's position if we can enough community support
> and complains at them :-)
>




  reply	other threads:[~2012-03-15 17:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 21:18 oe-core layer including support for i.MX28 Alex J Lennon
2012-03-15  7:17 ` Samuel Stirtzel
2012-03-15  8:27   ` Andreas Müller
2012-03-15  9:13     ` Alex J Lennon
2012-03-15 11:15 ` Otavio Salvador
2012-03-15 16:34   ` Alex J Lennon
2012-03-15 16:53     ` Otavio Salvador
2012-03-15 17:01       ` Alex J Lennon
2012-03-15 17:10         ` Eric Bénard
2012-03-15 17:16           ` Alex J Lennon
2012-03-15 17:21             ` Otavio Salvador
2012-03-15 17:26               ` Alex J Lennon [this message]
2012-03-15 18:16                 ` Otavio Salvador
2012-03-15 17:24             ` Eric Bénard

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=4F622652.30001@dynamicdevices.co.uk \
    --to=ajlennon@dynamicdevices.co.uk \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.