From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: generate a named kernel in ${DEPLOY_DIR_IMAGE}
Date: Wed, 29 Sep 2010 13:47:32 -0400 [thread overview]
Message-ID: <20100929174732.GA27217@denix.org> (raw)
In-Reply-To: <AANLkTikFQaRG3S8tJDGCFvWpad51Ac9X8f4DgHS-Rrvv@mail.gmail.com>
On Wed, Sep 29, 2010 at 08:28:37AM +0200, Frans Meulenbroeks wrote:
> 2010/9/29 Andrea Adami <andrea.adami@gmail.com>:
> > On Tue, Sep 28, 2010 at 6:54 PM, Frans Meulenbroeks
> >> As I needed to generate two different kernels for the same machine I
> >> had some kind of problem (as emailed yesterday).
> >> For now I've solved it as follows:
> >>
> >> I created a 2nd recipe (in an overlay):
> >> linux-small_2.6.34.bb
> >> this one essentially only requires linux_2.6.34.bb and sets S to the linux_${PN}
> >> Then I can just add a dir linux-small and add the small defconfig in it.
> >>
> >> That way bitbake linux-small should give me the 2nd kernel.
> >> And actually it builds the kernel but this one is also packaged in a
> >> kernel-*.ipk.
> >> I could have made two different machines, but that seemed somewhat
> >> overkill, so in the end I decided to modify do_install_append in
> >> linux.inc.
>
> PS: referring to Denys' message about multi-linux.inc: still haven't
> tested it, but what isslightly nasty about it is that it does not
> package, so I cannot easily include modules in an image
> (as my kernels are from the same recipe the modules are compatible,
> and it helps to be able to say in an image recipe that you want to add
> kernel-module-xyz)
Frans,
It packages only the main kernel and all the related modules, configured by
the usual defconfig file. But it doesn't do it for the additional kernels that
were built using configuration files from configs/ directory...
--
Denys
next prev parent reply other threads:[~2010-09-29 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 16:54 generate a named kernel in ${DEPLOY_DIR_IMAGE} Frans Meulenbroeks
2010-09-28 17:20 ` Denys Dmytriyenko
2010-09-28 17:59 ` Frans Meulenbroeks
2010-09-28 23:23 ` Andrea Adami
2010-09-29 6:28 ` Frans Meulenbroeks
2010-09-29 17:47 ` Denys Dmytriyenko [this message]
2010-09-29 19:19 ` Frans Meulenbroeks
2010-09-29 6:54 ` Frans Meulenbroeks
2010-09-29 11:44 ` Andrea Adami
2010-09-29 13:10 ` Frans Meulenbroeks
2010-09-29 15:18 ` Andrea Adami
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=20100929174732.GA27217@denix.org \
--to=denis@denix.org \
--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