I should probably mention, there is no need for much of a U-Boot script anymore. To boot with a uImage, my bootcmd is quite literally "tftpboot; bootm". Obviously we still have to do the same dance with plan9.ini, but I can live with that, though I do have some plans on how to deal with that later.
On Fri, Mar 29, 2013 at 9:17 AM, Steven Stallion <[email protected]>wrote: > U-Boot also performs relocation based on the load address which simplifies > the boot process. I'm working on an XIP kernel, which has cut around 100 > LOC out of l.s. It's a small change, but simplifies things considerably. > > > On Fri, Mar 29, 2013 at 3:19 AM, Richard Miller <[email protected]>wrote: > >> > Unlike Elf, the format is trivial. >> >> Not as trivial as raw binary, which we currently use for u-boot loading >> on most ARMs. The uImage format contains the load and entry address so >> you don't have to look up 'man 8 booting' or check the kernel mkfile >> before >> setting up the u-boot script. Are there any other advantages? >> >> >> >
