From: McClintock Matthew-B29882 <B29882@freescale.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Splitting processor and target in BSPs
Date: Fri, 2 Sep 2011 15:49:09 +0000 [thread overview]
Message-ID: <CAEsOVNd2i3Mn4zPdW5c1jRjKVwURUv9fYD3c_ghy+9gqsNgnsQ@mail.gmail.com> (raw)
In-Reply-To: <B1028606-FA51-475C-A6D5-6EBC31929292@keylevel.com>
On Fri, Sep 2, 2011 at 2:26 AM, Chris Tapp <opensource@keylevel.com> wrote:
> However, kernel configuration becomes a little bit more complicated as this
> is done by machine name. A kernel recipe will be needed for each machine
> (e.g. for the different sound drivers), but I can't work out how to do this
> using a base configuration for the SoCs that are shared and then adding
> machine specific parts. I can do it using (for example) a .defconfig for
> each machine, but that would require updates to multiple files to change the
> SoC configuration.
>
> I guess what I'm really asking is, is it possible to have a base CPU
> configuration and add a machine configuration to this ?
>
> I've recently seen discussion of .cfg kernel fragment files. Are these what
> I should be looking at? Are these available in the releases or only in the
> development branch?
I think this is a good solution for you. It's a little confusing to
find were this work is but you can look in the linux-yocto kernel tree
- then the actual cfg fragment stuff on different branches.
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/
meta branch contains meta/ which contains a lot of the cfg fragments,
and patches, etc. There is also a document in the git repo as well
which is worth a look.
-M
next prev parent reply other threads:[~2011-09-02 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 7:26 Splitting processor and target in BSPs Chris Tapp
2011-09-02 15:48 ` Bruce Ashfield
2011-09-02 15:49 ` McClintock Matthew-B29882 [this message]
2011-09-03 11:32 ` Chris Tapp
2011-09-03 14:40 ` Bruce Ashfield
2011-09-02 19:39 ` Tom Zanussi
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=CAEsOVNd2i3Mn4zPdW5c1jRjKVwURUv9fYD3c_ghy+9gqsNgnsQ@mail.gmail.com \
--to=b29882@freescale.com \
--cc=opensource@keylevel.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.