From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: kernels
Date: Fri, 15 Jul 2011 16:02:54 +0100 [thread overview]
Message-ID: <1310742175.30326.1.camel@phil-desktop> (raw)
In-Reply-To: <CADkTA4OYB0mch1SRSgidwGfZiWBeBuaWKH1BU1NgF9jPVa1Niw@mail.gmail.com>
On Fri, 2011-07-15 at 09:51 -0400, Bruce Ashfield wrote:
> On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <pb@pbcl.net> wrote:
> > The other day I was working on a BSP layer for a fairly generic i586
> > system and I was struck by the fact that we don't appear to have any
> > vanilla kernel recipes in oe-core. I had sort of expected that, to get
> > a standard bzImage out, I would just need to ship an appropriate
> > defconfig in my layer and everything else would "just work".
>
> Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto
> kernel base can work in this mode, since that was a design goal of
> 1.0.
>
> You pick a branch, throw in a config fragment (or defconfig if you really
> want) and build. The base branches in the tree are generic enough to
> sort a range of boards out of the box, and should form a base.
Okay, cool. I'll give it a go and see how I get on.
Is there a description anywhere of what the functional differences are
between the code in linux-yocto git and the upstream kernel.org tree?
p.
next prev parent reply other threads:[~2011-07-15 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 13:21 kernels Phil Blundell
2011-07-15 13:51 ` kernels Bruce Ashfield
2011-07-15 15:02 ` Phil Blundell [this message]
2011-07-15 15:36 ` kernels Bruce Ashfield
2011-07-20 15:42 ` kernels Bruce Ashfield
2011-07-20 15:45 ` kernels Koen Kooi
2011-07-20 19:47 ` kernels Bruce Ashfield
2011-07-21 17:23 ` kernels Anders Darander
2011-07-21 17:36 ` kernels Bruce Ashfield
2011-07-21 20:28 ` kernels Anders Darander
2011-08-15 20:52 ` kernels Bruce Ashfield
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=1310742175.30326.1.camel@phil-desktop \
--to=philb@gnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox