From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: Updating u-boot for oe-core or meta-yocto
Date: Wed, 25 May 2011 11:40:27 -0700 [thread overview]
Message-ID: <4DDD4D1B.5050301@linux.intel.com> (raw)
In-Reply-To: <20110525164919.GB11519@mail.familie-heinold.de>
On 05/25/2011 09:49 AM, Henning Heinold wrote:
> Hi,
>
> I agree with khem, each machine should maintain it's bootloader in his bsp
> or layer.
I'm leaning this way as well. I think oe-core should remain at an
official u-boot tagged release, like 2011.03 and layers can then extend
that with a proper .bbappend file. Then we can share the u-boot core
recipe and just add backported patches in the layers as needed.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-05-25 18:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 16:36 Updating u-boot for oe-core or meta-yocto Darren Hart
2011-05-24 17:13 ` Koen Kooi
2011-05-24 18:04 ` Darren Hart
2011-05-24 17:23 ` Khem Raj
2011-05-24 17:51 ` adding meta-intel layers breaks parsing, was " Koen Kooi
2011-05-24 18:07 ` Tom Zanussi
2011-05-25 14:28 ` Tom Zanussi
2011-05-25 14:31 ` Koen Kooi
2011-05-25 14:38 ` Phil Blundell
2011-05-25 14:52 ` Tom Zanussi
2011-05-25 18:56 ` Darren Hart
2011-05-25 19:11 ` Phil Blundell
2011-05-25 20:04 ` Darren Hart
2011-05-25 21:31 ` Richard Purdie
2011-05-25 23:18 ` Darren Hart
2011-05-24 18:23 ` Darren Hart
2011-05-24 18:35 ` Khem Raj
2011-05-24 18:48 ` Phil Blundell
2011-05-24 19:33 ` Darren Hart
2011-05-24 17:33 ` Martin Jansa
2011-05-25 15:51 ` Richard Purdie
2011-05-25 16:36 ` Khem Raj
2011-05-25 16:49 ` Henning Heinold
2011-05-25 18:40 ` Darren Hart [this message]
2011-05-26 6:12 ` Anders Darander
2011-05-26 13:54 ` Darren Hart
2011-05-25 21:51 ` Richard Purdie
2011-05-25 23:31 ` Jason Kridner
2011-05-26 18:07 ` Darren Hart
2011-05-27 5:36 ` Anders Darander
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=4DDD4D1B.5050301@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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.