From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: using initramfs with openembedded.
Date: Tue, 23 Feb 2010 10:03:51 +0100 [thread overview]
Message-ID: <hm05ln$2cr$1@dough.gmane.org> (raw)
In-Reply-To: <18e217241002221429m1939c786u52da4672f626ca07@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 22-02-10 23:29, C Michael Sundius wrote:
> We'd like to put our initial boottime file system into the initramfs in the
> kernel. But we also need to build some separate drivers to put into that
> filesystem image.
>
> Of course we can't build those drivers without the kernel staging dir
> populated. (which doesn't happen until after the build of the kernel).
>
> Has anyone run into this problem? how did you solve it? do I need to stage
> the headerfiles and config info before the kernel build?
>
> maybe this problem is solved some other way.. I haven't really tried this so
> I'm just speculating here.
>
> If anyone has some experience with this it would be great to hear how to go
> about this. thanks for you help
The common way right now is to use 2 kernel recipes. Not an optimal
situation, but it will get you there.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLg5n3MkyGM64RGpERAt6HAJ95plgifYy7yqC6mjovarzuokEPjwCgg0R1
d8Lfns4Aq/S9rwyV930RjME=
=2fyI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-02-23 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 22:29 using initramfs with openembedded C Michael Sundius
2010-02-23 9:03 ` Koen Kooi [this message]
2010-02-23 9:19 ` Graeme Gregory
2010-03-02 22:42 ` C Michael Sundius
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='hm05ln$2cr$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 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.