It might not be limited to FAT but uboot definitely has a flag for considering an environment file on an MMC fat partition - maybe there's an ext2 one too, I didn't check. But it's to solve the problem of having to store u-boot environment otherwise on raw blocks which means reserving space (pain in the backside on OMAP as MLO/X-Loader etc. are notoriously finicky). Since it knows FAT, or a restricted subset of FAT, the uEnv.txt gets put with the rest of the loader files...
-- Matt Sealey <[email protected]> Product Development Analyst, Genesi USA, Inc. On Aug 9, 2012, at 10:37 AM, Stephen Warren <[email protected]> wrote: > On 08/08/2012 09:37 PM, Matt Sealey wrote: >> uEnv.txt and boot.scr aren't the same thing. uEnv.txt is the U-Boot >> environment usually on a fat partition. > > I have no idea why it'd be limited to FAT; it's just a file... > >> boot.scr is loaded by a readily loaded environment... You either >> predefined your environment and boot from it or you're using values >> from that environment. I wouldn't use uEnv.txt to replace a >> boot.scr on any system.. > > I'd view uEnv.txt as simply a different way of writing a boot script. > "env import" has a -d option which appears to merge the loaded > environment into the current environment, rather than completely > replacing the environment. I could easily imagine loading uEnv.txt, > expecting it to define some specific variable/macro containing the > subsequent boot commands, and then "run"ing that variable. _______________________________________________ cross-distro mailing list [email protected] http://lists.linaro.org/mailman/listinfo/cross-distro
