Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "G. Eismann" <g.eismann@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: adding new kernel defconfig
Date: Sun, 19 Apr 2009 17:55:32 +0200	[thread overview]
Message-ID: <200904191755.32769.g.eismann@gmx.net> (raw)
In-Reply-To: <200904191401.26942.mickey@vanille-media.de>

El Sunday 19 April 2009 14:01:26 Michael 'Mickey' Lauer escribió:
> On Sunday 19 April 2009 13:54:07 G. Eismann wrote:
> > Hi there,
> >
> > I am new with openembedded and I am trying to build a kernel for a new
> > machine.
> >
> > In my machine config file I have these lines:
> >
> > PREFERRED_PROVIDER_virtual/kernel = "linux"
> > PREFERRED_VERSION_linux = "2.6.25"
> >
> > When I build the kernel, bitake downloads a 2.6.25 kernel: OK
> > But it takes the kernel config from recipes/linux/linux/defconfig
> >
> > I have added my own defconfig file in
> > recipes/linux/linux-2.6.25/mymachine/defconfig but I dont know how to say
> > bitbake to use it.
>
> If you have set MACHINE=mymachine and are using a DISTRO configuration
> which includes a reasonable set of OVERRIDES; then $MACHINE is included in
> these OVERRIDES; which means, bitbake will copy $MACHINE/defconfig (if
> present) into $WORKDIR.
>

MACHINE is set in my local.conf file.
I've also added a line with DEFAULT_PREFERENCE_mymachine = "1" to 
linux_2.6.25.bb although I am not sure if this is correct.

The DISTRO configuration had no OVERRIDES line. I have copied the OVERRIDES 
line from minimal distro ($MACHINE is included in it), but bitbake is still 
taken the defconfig from linux/defconfig

  - Eismann -
 



      reply	other threads:[~2009-04-19 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 11:54 adding new kernel defconfig G. Eismann
2009-04-19 12:01 ` Michael 'Mickey' Lauer
2009-04-19 15:55   ` G. Eismann [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=200904191755.32769.g.eismann@gmx.net \
    --to=g.eismann@gmx.net \
    --cc=openembedded-devel@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