[oe] Kernel image stagging [was Re: [PATCH] kernel.bbclass: Stage the raw zImage and modules tarball for inclusion in pstage

[Tom Rini]

On Tue, 2010-02-23 at 16:41 -0300, Otavio Salvador wrote:
> Hello,
> 
> On Tue, Feb 23, 2010 at 4:23 PM, Tom Rini <tom_rini at mentor.com> wrote:
> 
> >  In the second case, why do I want to waste space with an image on the
> > rootfs that I don't need?  Today, that image goes from deploy dir to
> > <however we give stuff to the end user> or right to the device.  I could
> > see, however, adding images to a defined place in meta-toolchain so that
> > this isn't an issue anymore and we could stop putting raw kernel stuff
> > into the deploy directory.
> >
> 
> I think that a binary fine, copied from the built package, in deploy dir is
> wrong by conception. It ought to be puted there as an image, if it is needed
> by an image.

What do you mean by an image?  a uImage is an image.  Sure, there's a
corner case where you put a raw vmlinux into flash but...  But what I'm
saying is that you need a kernel ready for use somewhere.  I could live
with it coming out of meta-toolchain, but that's ugly.

As a use case, I configure for beagleboard.  I bitbake console-image.  I
stick console-image.tar.bz2 onto partition 2 of my SD card.  I grab my
kernel from where? and stick it onto partition 1 so that I can put it
into the beagleboard and mmc init;run loaduimage;run mmcboot.

-- 
Tom Rini <tom_rini at mentor.com>
Mentor Graphics Corporation