Re: Providing (armhf) u-boot images together with d-i images?
On Sat, Dec 06, 2014 at 01:07:35PM -0600, Robert Nelson wrote:
> omap bootrom's with the introduction of the omap4 can be dd'ed liked
> dd if=MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k
> dd if=u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k
omap5 seems to have the MLO at 512 bytes from the start, so 128k would
certainly not match in that case. More common seems to be the use of a
"boot" partition with the files instead.
> That just leaves the omap3 family (BeagleBoard (omap34/35xx) &
> BeagleBoard xM (omap36xx/DM3730) stuck with reading the MLO/u-boot.img
> on "boot"* partition.
> * mainline u-boot now has patches to enable extX boot vs fat boot, but
> it's an either "or" situation based on sram memory size..
At least it gives some choice.