From: Michael Krelin <hacker@klever.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] make building working zaurus images easier
Date: Thu, 26 Jul 2007 15:19:35 +0200 [thread overview]
Message-ID: <46A89F67.5080907@klever.net> (raw)
In-Reply-To: <46A88A22.5010608@dominion.kabel.utwente.nl>
I have never looked into all this machinery, but since we have, e.g.
x11-image-spitz.tar.gz and zImage-spitz.bin symlinks, I'd guess that we
can do without these somewhat ugly when unnecessary `ls|sort|uniq|tail`
things, can't we?
Love,
H
Koen Kooi wrote:
> -----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-----
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2007-07-26 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 11:48 [RFC] make building working zaurus images easier Koen Kooi
2007-07-26 11:57 ` Marcin Juszkiewicz
2007-07-26 12:11 ` Koen Kooi
2007-07-26 12:30 ` Richard Purdie
2007-07-26 12:44 ` Koen Kooi
2007-07-26 13:19 ` Michael Krelin [this message]
2007-07-26 16:51 ` Richard Purdie
2007-07-26 17:36 ` Koen Kooi
2007-07-26 18:04 ` Michael Krelin
2007-07-26 18:39 ` Richard Purdie
2007-07-27 8:26 ` Koen Kooi
2007-07-27 8:47 ` Michael Krelin
2007-07-27 9:54 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A89F67.5080907@klever.net \
--to=hacker@klever.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.