All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Additional / new BSP collection?
Date: Wed, 27 Jul 2011 14:52:03 +0100	[thread overview]
Message-ID: <1311774723.2344.373.camel@rex> (raw)
In-Reply-To: <4E3012D8.3080106@windriver.com>

On Wed, 2011-07-27 at 09:30 -0400, Bruce Ashfield wrote:
> As you know, I've been working on several kernel efforts
> around the FSL parts as well (in particular the ones that
> have enough pieces upstream to work out of the box).  I
> definitely don't want to overlap in a way that doesn't
> create complimentary efforts.
> 
> What are your current thoughts around kernels and the
> (nearly religious) kernel version question ? It would be
> great to get some alignment on features (-rt, tracing,
> boot, footprint reduction, etc, etc) and save some effort
> on maintenance and validation. Also if we want to create
> some yocto reference BSPs, having a kernel version and feature
> set match is important as well (i.e. what we've done for
> the intel ones).
> 
> To that end, do you have an thoughts about using linux-yocto
> as a base to any BSP work ? That statement doesn't do it
> justice though, since when I say 'use linux-yocto as a base',
> it really means that linux-yocto uses your BSPs as an
> upstream/official reference and can pull support for them
> into branches, and have the configuration and other tooling
> get them any functionality that is being developed.
> 
> No control over BSP content, or anything like this, is being
> suggested or asserted here. Just looking to all push in the
> same direction (embedded features and BSPs to upstream) and
> re-use the work of BSPs available in the community. If the
> base is the same (and hence kernel version), then this relationship
> and workflow is very simple.
> 
> ... and as a bonus, if the workflow doesn't work easily, then
> there's a problem with it and we can work on something that
> is suitable (change tools, etc).

So just to put what Bruce says into other words, there isn't any hard
requirement to use linux-yocto but we are asking people to try it and if
it doesn't work, at least tell us why.

I understand transitions and new ways of working take time and that
meta-fsl-ppc might be enough of a step at first without the linux-yocto
complications. That is fine but please do keep it in mind.

Cheers,

Richard



  reply	other threads:[~2011-07-27 13:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27  5:21 Additional / new BSP collection? Kumar Gala
2011-07-27  8:45 ` Richard Purdie
2011-07-27 12:40   ` Kumar Gala
2011-07-27 13:30     ` Bruce Ashfield
2011-07-27 13:52       ` Richard Purdie [this message]
2011-07-27 13:55       ` Kumar Gala
2011-07-27 14:23         ` Richard Purdie
2011-07-27 14:58           ` Bruce Ashfield
2011-07-27 13:50     ` Tom Zanussi
2011-07-27 13:53       ` Kumar Gala
2011-07-27 14:06         ` Tom Zanussi
2011-07-27 14:13           ` Kumar Gala
2011-07-27 14:33           ` Cherry, John

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=1311774723.2344.373.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@windriver.com \
    --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.