All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
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 16:39:55 +0100	[thread overview]
Message-ID: <1311781195.2344.398.camel@rex> (raw)
In-Reply-To: <0871F19F-E6BF-481E-920E-87091DEF7F49@kernel.crashing.org>

On Wed, 2011-07-27 at 09:23 -0500, 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).
> 
> Than everything else would live in the meta-fsl-ppc layer.

The original criteria for what we included was:

* One board per architecture
* Should be available to a general developer in a relatively cost 
  effective manner (sub $1000?)
* Lets us test functionality of the architecture

Trying to find a PPC board we could easily obtain was quite tricky. We
stuck to one board per architecture for fairness reasons and also
resources since the Yocto project isn't resourced to maintain BSPs.

We're definitely open to discussions about changes there but it does
need to be a high level discussion, likely at the advisory board level.

Note that some of Yocto's developers and the QA team have those
reference board for test purposes so if we do change we'd need to update
their hardware.

Cheers,

Richard




      parent reply	other threads:[~2011-07-27 15:40 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
2011-07-27 15:39 ` Richard Purdie [this message]

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=1311781195.2344.398.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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.