On Friday 06 August 2010 14:25:53 Wookey wrote:
> +++ Charles Manning [2010-08-06 14:21 +1200]:
> > Very confusing for the newbie...
> >
> >
> > http://www.balloonboard.org/balloonwiki/SoftwareBuilding
> >
> > The CROSS_COMPILE=arm-linux-gnu- bit is out of date
>
> True.
>
> It's a wiki, so do please fix any such things you find. (I've fixed
> that particualr point, but if you are going through trying to follow
> it you will have a much better idea which bits are wrong, inadequate
> or confusing.)

I've just figured out a wonky workflow for building and testing **just** the 
kernel. I'll write that up.

At present it is like this:

Once off: 
1) pull svn, do all the software loading giving a box that runs current svn.

2) Get rid of old kernel yaffs2
rm -rf /opt/balloon/build/kernel/<ver>/fs/yaffs2
3) Link the kernel tree to the experimental yaffs tree
cd /opt/y/git/yaffs2
patch-ker.sh l /opt/balloon/build/kernel/<ver>

This is linked, rather than copied so that changes in the yaffs tree are seen 
by kernel builds.

Per hacking event
Make changes in /opt/y/git/yaffs2
cd /opt/balloon/build/kernel/<ver>
ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make zImage
cp arch/arm/boot/zImage /opt/balloon/distro/binaries/kernel/
cd /opt/balloon/distro/binaries
utils/bblrc --kernel


Reboot. Look ma, new yaffs.

That's working, but is rather convoluted. Not too bad if you do it from three 
different terminals. Is it the right way to do this? I'm sure nobody would 
put up with this on a regular basis so I expect there's a far slicker 
workflow out there.

I also tried doing make, make distro etc but that caused a bun-fight with 
quilting et al that either gave me no yaffs or the old yaffs.



-- Charles