[oe] [RFC] make building working zaurus images easier

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Building a working zaurus image is tedious since you have *manually* rename a bunch of
files before the on-board flashing software will accept it.

I therefore want to propose 2 small scripts that can be run as EXTRA_IMAGECMD to make life
a lot easier for both developers and users:

[beware of line wrapping]

For c7x0:

#!/bin/sh
cd ${DEPLOY_DIR_IMAGE}
mkdir ${IMAGE_NAME}-installkit/
cp `ls zImage-2* | sort -b | uniq |tail -n1` ${IMAGE_NAME}-installkit/zImage.bin
cp `ls ${IMAGE_NAME}.rootfs*jffs2 | sort -b | uniq |tail -n1`
${IMAGE_NAME}-installkit/initrd.bin
cp updater.sh.${MACHINE} ${IMAGE_NAME}-installkit/updater.sh
tar cjf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit.tar.bz2
${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit/
rm -rf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit/


For Spitz:

#!/bin/sh
cd ${DEPLOY_DIR_IMAGE}
mkdir ${IMAGE_NAME}-installkit/
cp `ls zImage-2* | sort -b | uniq |tail -n1` ${IMAGE_NAME}-installkit/zImage.bin
cp `ls ${IMAGE_NAME}.rootfs*gz | sort -b | uniq |tail -n1`
${IMAGE_NAME}-installkit/hdimage1.tgz
cp updater.sh.${MACHINE} ${IMAGE_NAME}-installkit/updater.sh
cp gnu-tar ${IMAGE_NAME}-installkit/
tar cjf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit.tar.bz2
${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit/
rm -rf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit/


These are just proof of concept scripts, but would something like this be acceptable to
the zaurus maintainers in OE? Having something like this would make live for distro people
a lot easier and should confuse OE newbies a bit less.

I have added something similar for bootldr based ipaqs in OE that writes out a reflash.ctl
automagically, which has been a great success.

Comments/improvements/flames?

regards,

Koen



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGqIoiMkyGM64RGpERApzOAJ9LGbvsDEOdsILrWbausHIFB8gCxACeIrR+
53PH8E27hgzdmkaYtC4EciE=
=6q4E
-----END PGP SIGNATURE-----