On Tue, Aug 24, 2010 at 11:28 AM, Dave Martin <dave.mar...@linaro.org> wrote: > Hi, > > On Mon, Aug 23, 2010 at 11:20 PM, Loïc Minier <loic.min...@linaro.org> wrote: > > [...] > >> >> a kernel build most commonly outputs a zImage; this is then converted >> to an uImage for u-boot consumption with some rune like: >> mkimage -A arm -O linux -T kernel -C none \ >> -a 0x80008000 -e 0x80008000 -n Linux \ >> -d vmlinuz-2.6.35-1001-omap \ >> uImage-linaro > > Couldn't we simply use the kernel tree "make uImage" rule, and put the > uImage in the kernel binary packages, rather than reduplicating this > elsewhere? Of course, which kernel tree targets to build may then > become board-specific, which might be seen as a disadvantage.
As you rightly pointed out, every arch/bootloader combination could then have a different potentional target image format. So the kernel package sticks to the simplicity of generating a zImage. And flash-kernel(?) has the logic of converting the zImage into whatever format is acceptable to the bootloader. > I've tended to treat the kernel tree rule as the canonical way of > generating a valid uImage, though maybe not everyone will agree with > that. I use it for my own kernels too. /Amit _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
