[oe] RFC: making uboot safe for multimachine and agree on one spelling
Harald Welte
laforge at openmoko.org
Fri Feb 16 21:02:11 UTC 2007
On Fri, Feb 16, 2007 at 07:00:47PM +0100, Koen Kooi wrote:
> After spending some time going trough u-boot recipes trying to make sense of its
> buildsystem, I noticed some strange problems and inconsistencies.
>
> First the easy part: we need *one* spelling for u-boot, instead of uboot, u-boot, u-bot,
> etc. What is the preferred one nowadays?
u-boot is the official name, so I would recommend to go for that (even
though I hate hyphens inside project names)
> Second: it seems that the 'mkimage' tool is at least arch speficic (at worst
> board-specific), so uboot recipes should install it to
> ${STAGING_NATIVE_DIR}/mkimage.u-boot.${MACHINE_ARCH}
are you sure it's arch specific? I'm quite surprised about that, since
the uImage format contains a header indicating the architecture, doesn't
it?
If it really uses a different binary format for each arch, yes, we
should change it. 'mkuimage.${MACHINE_ARCH}' sounds like a more user
friendly name, though.
--
- Harald Welte <laforge at openmoko.org> http://openmoko.org/
============================================================================
Software for the world's first truly open Free Software mobile phone
More information about the Openembedded-devel
mailing list