>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.
(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 :)
Alex/
On 15/03/2012 17:10, Eric Bénard wrote:
Hi,
Le Thu, 15 Mar 2012 17:01:07 +0000,
Alex J Lennon<[email protected]> a écrit :
Is the the new machine target and associated recipes, kernel+patches
something that I should expect to be able to merge back into
meta-fsl-arm at some point?
that depends if meta-fsl-arm is considered as the layer for supporting
evaluation boards from Freescale of the layer which can host any board
using a Freescale i.MX.
I think the first solution is better and that custom boards should
be added to custom layers (maybe on top of meta-fsl-arm if these custom
boards need recipes included in the reference layer).
Eric
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
