diff options
| author | Simon Glass <sjg@chromium.org> | 2012-10-25 16:31:11 +0000 |
|---|---|---|
| committer | Gerald Van Baren <gvb@unssw.com> | 2012-11-12 23:14:57 -0500 |
| commit | fcabc24f4fd2fd581036c7a20eee47a204f04f39 (patch) | |
| tree | 2d534f1bb42bf9890ee233d2a7ae9865f888ed29 /doc/README.m28 | |
| parent | d95f6ec7334076a1e4b13f3748ebfd1b58ac90f6 (diff) | |
| download | u-boot-imx-fcabc24f4fd2fd581036c7a20eee47a204f04f39.zip u-boot-imx-fcabc24f4fd2fd581036c7a20eee47a204f04f39.tar.gz u-boot-imx-fcabc24f4fd2fd581036c7a20eee47a204f04f39.tar.bz2 | |
fdt: Set kernaddr if fdt indicates a kernel is present
If kernel-offset is specified in the fdt, set an environment variable
so that scripts can access the attached kernel.
This can be used by a packaging program to tell U-Boot about a kernel
that has been downloaded alongside U-Boot. The value in the fdt is
the offset of the kernel from the start of the U-Boot image, so we can
find it just by adding CONFIG_SYS_TEXT_BASE.
It is then fairly easy to put something like this in the environment
variables in the board header file:
"if test ${kernaddr} != \"\"; then "\
"echo \"Using bundled kernel\"; "\
"bootm ${kernaddr};" \
"fi; "\
/* rest of boot sequence follows here */
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/README.m28')
0 files changed, 0 insertions, 0 deletions