From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: BSP in meta layer vs poky
Date: Wed, 27 Jul 2011 11:04:15 -0400 [thread overview]
Message-ID: <4E3028EF.2000302@windriver.com> (raw)
In-Reply-To: <0871F19F-E6BF-481E-920E-87091DEF7F49@kernel.crashing.org>
On 07/27/11 10:23, Kumar Gala wrote:
> I was wondering what distinction qualified for a BSP existing in a meta layer vs in poky directly.
>
> For FSL PPC we currently have MPC8315-RDB in poky. Ideally we'd have one BSP for each major flavor [ associated with a unique compiler / libc target ]. This would end up being something like P2020-RDB (e500v2 core), P204x-RDB (e500mc core), P5020DS (e5500 core - 32/64 bit).
This sort of coverage would be great, and your options
would be the big ones on my hit list as well. It allows
us to at the least ensure that the build coverage is
complete.
>
> Than everything else would live in the meta-fsl-ppc layer.
This makes sense as well.
There are some other options. The BSPs that you see embedded
in meta-yocto could all be split out into layers. It's largely
a matter of time, effort and benefit. There is the risk of
over segmentation and 'layerization', but we aren't there yet.
The point I'm trying to make here is that if a BSP aligns with
linux-yocto and is one that we are actively using as a reference,
it can be directly in meta-yocto or in another layer and it
will work equally well.
Cheers,
Bruce
>
> - k
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2011-07-27 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 14:23 BSP in meta layer vs poky Kumar Gala
2011-07-27 15:04 ` Bruce Ashfield [this message]
2011-07-27 15:39 ` Richard Purdie
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=4E3028EF.2000302@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=galak@kernel.crashing.org \
--cc=yocto@yoctoproject.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.