using initramfs with openembedded.

using initramfs with openembedded.

[C Michael Sundius]

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

Mike

Re: using initramfs with openembedded.

[Koen Kooi]

-----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-----

Re: using initramfs with openembedded.

[Graeme Gregory]

On Tue, Feb 23, 2010 at 10:03:51AM +0100, Koen Kooi wrote:
> -----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.
> 

I think it should be possible to write an initramfs.bbclass and use
BBCLASSEXTEND to make it simpler.

Graeme

Re: using initramfs with openembedded.

[C Michael Sundius]

On Tue, Feb 23, 2010 at 1:03 AM, Koen Kooi <k.kooi@student.utwente.nl>wrote:

> -----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.
> >
>
> The common way right now is to use 2 kernel recipes. Not an optimal
> situation, but it will get you there.
>
> Back to this question, using two kernel recipes would create two machine
specific directories under tmp/work/

tmp/work/boot-kenrel/(kernel and modues)
tmp/work/run-time-kenrel/(kernel and modules)

so we'd still have to build all the modules twice too... is that right? I
guess we'd install the boot-modules into the initramfs, and throw away that
kernel.

then we'd link the initramfs into the runtime kenrel.

finally we'd install the runtime modules into the runtime filesystem....