From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org, poky@yoctoproject.org, saul.wold@intel.com
Subject: Re: [PATCH 0/1] linux-yocto/stable: streamline BSP processing
Date: Wed, 09 Feb 2011 11:12:57 +0000 [thread overview]
Message-ID: <1297249977.1395.6323.camel@rex> (raw)
In-Reply-To: <cover.1297232160.git.bruce.ashfield@windriver.com>
Hi Bruce,
On Wed, 2011-02-09 at 01:22 -0500, Bruce Ashfield wrote:
> The subject is a bit deceiving, since the 'streamlining' that I've been
> working on for BSP / external board building for a while, actually
> solves a lot of the SRCREV/race conditions that we've been seeing.
>
> With the new fetcher and some factoring of the code, I've been able
> to delete 99% of the anonymous python and simply the processing
> for new BSPs.
>
> To create a BSP against the yocto kernels all one must do is put
> the variable YOCTO_KERNEL_EXTERNAL_BRANCH and indicate the branch
> name that should be used. The tools and processing does the rest.
>
> I built all existing boards, and bootstrapped a BSP against the
> stable and devel yocto kernels while testing this. Everything
> worked well.
>
> Darren: I haven't touched the preempt_rt recipes (yet), but we
> can streamline them as well.
>
> This is the first step in some other refactoring and cleanups for
> easier inclusion of the yocto kernel parts, but we'll let this
> soak first before stacking more changes on top.
Looks good, nice to see this cleaning up, thanks! :)
Cheers,
Richard
prev parent reply other threads:[~2011-02-09 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 6:22 [PATCH 0/1] linux-yocto/stable: streamline BSP processing Bruce Ashfield
2011-02-09 6:22 ` [PATCH 1/1] linux-yocto: streamline BSP bootstrapping Bruce Ashfield
2011-02-09 11:14 ` Richard Purdie
2011-02-09 14:00 ` Bruce Ashfield
2011-02-09 11:12 ` 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=1297249977.1395.6323.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.org \
--cc=saul.wold@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox