mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-28 07:31:15 +00:00
95fd977201
It can be useful to use the same U-Boot binary for multiple purposes, say the normal one, one for developers that allow breaking into the U-Boot shell, and one for use during bootstrapping which runs a special-purpose bootcmd. Or one can have several board variants that can share almost all boot logic, but just needs a few tweaks in the variables used by the boot script. To that end, allow the control dtb to contain a /config/enviroment node (or whatever one puts in fdt_env_path variable), whose property/value pairs are used to update the run-time environment after it has been loaded from its persistent location. The indirection via fdt_env_path is for maximum flexibility - for example, should the user wish (or board logic dictate) that the values in the DTB should no longer be applied, one simply needs to delete the fdt_env_path variable; that can even be done automatically by including a fdt_env_path = ""; property in the DTB node. Reviewed-by: Simon Glass <sjg@chromium.org> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk> Acked-by: Joe Hershberger <joe.hershberger@ni.com> |
||
|---|---|---|
| .. | ||
| attr.c | ||
| callback.c | ||
| common.c | ||
| eeprom.c | ||
| embedded.c | ||
| env.c | ||
| ext4.c | ||
| fat.c | ||
| flags.c | ||
| flash.c | ||
| Kconfig | ||
| Makefile | ||
| mmc.c | ||
| nand.c | ||
| nowhere.c | ||
| nvram.c | ||
| onenand.c | ||
| remote.c | ||
| sata.c | ||
| sf.c | ||
| ubi.c | ||