aef04a8aa1
Instead of using an hard coded address, make use of an already defined address for importing the environment for ramfs and nfs boot. This allows boards having different mapping to use the same code. CC: Heiko Schocher <hs@denx.de> CC: Tom Rini <trini@konsulko.com> Signed-off-by: Matteo Ghidoni <matteo.ghidoni@hitachi-powergrids.com> Signed-off-by: Holger Brunck <holger.brunck@hitachi-powergrids.com> |
||
---|---|---|
.. | ||
develop-arm.txt | ||
develop-common.txt | ||
develop-ppc_8xx.txt | ||
develop-ppc_82xx.txt | ||
ramfs-arm.txt | ||
ramfs-common.txt | ||
ramfs-ppc_8xx.txt | ||
ramfs-ppc_82xx.txt | ||
README |
These scripts are needed for our development usecases. Copy this directory into your tftp root directory to be able to use this scripts. cp -r <u-boot-repo>/board/keymile/scripts <your_tftp_root>/ To load and configure these usecase, two environment variables in the u-boot default environment must be parsed: run develop : setup environment to configure for rootfs via nfs run ramfs : setup environment to configure for rootfs in ram Last change: 24.11.2011 develop-common.txt ============================ This file defines variables for working with rootfs via nfs for powerpc and arm. develop-<arch>.txt ============================ This file defines architecture specific variables for working with rootfs via nfs arm. ramfs-common.txt ============================ This file defines variables for working with rootfs inside the ram for powerpc and arm. ramfs-<arch>.txt ============================ This file defines architecture specific variables for working with rootfs inside ram.