[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 17:18 -0300, Otavio Salvador wrote:
> Hello,
> 
> On Tue, Feb 23, 2010 at 5:12 PM, Tom Rini <tom_rini at mentor.com> wrote:
> 
> > 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.
> >
> 
> I see your point and I'm not saying we shouldn't have the kernel available
> somewhere. We need it somewhere.
> 
> However I disable when it is copied to deploy; in my opinion it ought to be
> done at rootfs creation so it will _always_ have a {z,bz,u}Image available
> in deploy dir.
> 
> Just try:
> 
> bitbake console-image (works)
> rm $DEPLOY_DIR
> bitbake console-image (fails)
> 
> and this is wrong IMO.

No, it works today since I was bad (and forgot the policy about getting
acks) and just fixed it.  That said, I'll admit I'm not 100% sure that
everything is correct in other cases.  We've caught the uImage case, but
I'm thinking device trees are probably broken.  So, a PoC patch to get
image.bbclass to do something sane to DEPLOY_DIR would be fine with me,
if I don't get to it first ;)

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