On Mon, 31 Jan 2011 21:18:35 +0100 Wolfgang Denk <w...@denx.de> wrote:
> Dear Scott Wood, > > In message <20110131140801.33609...@udp111988uds.am.freescale.net> you wrote: > > > > > Please rather omit the setting instead of using fillers that are of no > > > practical value. > > > > Well, they do make it easier for a user to quickly see what the names > > are that U-Boot expects for such commonly used things, rather than > > having to scan the manual. > > I doubt both the "quicly see" part (in such a long list of settings) > and the "rather than having to scan the manual" part. I've found it convenient, along with the more meaningful error messages if I forget to replace one of them. YMMV. > > > > + "ramdiskfile=your.ramdisk.u-boot\0" > > > > \ > > > > > > Ditto. [BTW: why "....ramdisk.u-boot"? U-Boot does not use ramdisks. > > > The ramdisk is only used for some OS, so that should probably be > > > "...ramdisk.linux" instead?] > > > > We often use the ".u-boot" suffix on ramdisks that have been wrapped > > with a uImage header. > > That would be a "uRamdisk" then (similar to uImage). Is anyone actually calling it that? What if I have multiple ramdisk images that I want to call different names? FWIW, for non-Linux OS images we sometimes use .uImage as a suffix. -Scott _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
