diff options
author | Zhang Jiejing <jiejing.zhang@freescale.com> | 2012-02-15 16:40:33 +0800 |
---|---|---|
committer | Lily Zhang <r58066@freescale.com> | 2012-02-27 12:59:45 +0800 |
commit | c530d9188dbf0d97cab4b38f0a53a28c56a6bd6c (patch) | |
tree | 8a6d3d2e45d4a6a7964e6ae110654aa341a8b576 /include/kgdb.h | |
parent | 72e8b5a4858d802d5135ba0d4b41ea9554a8c987 (diff) | |
download | u-boot-imx-c530d9188dbf0d97cab4b38f0a53a28c56a6bd6c.zip u-boot-imx-c530d9188dbf0d97cab4b38f0a53a28c56a6bd6c.tar.gz u-boot-imx-c530d9188dbf0d97cab4b38f0a53a28c56a6bd6c.tar.bz2 |
ENGR00174536-1 booti: add booti command support.
Support booti command which can boot from a boot.img
boot.img is a zImage + ramdisk.img + bootargs + boot addr
which include these info can be used to avoid mis match between
kernel and ramdisk, also can avoid commit to chagne default
bootargs.
For example:
> booti mmc1
command will read the boot.img from 1M offset,
and then parser the bootargs and ramdisk
then do the boot from that zImage.
> booti mmc1 recovery
will going to read the recovery's partition no
and offset and boot from recovery image.
this recovery image also a zImage + ramdisk
bootargs:
if uboot have define a env var 'bootargs', booti command
will use this bootargs as kernel cmdline
if you want use boot.img 's bootargs, just type:
> setenv bootargs
in uboot to clear the bootargs in uboot env.
our default uboot env will be NULL in config file.
also, android use boot.img to support OTA.
Signed-off-by: Zhang Jiejing <jiejing.zhang@freescale.com>
Diffstat (limited to 'include/kgdb.h')
0 files changed, 0 insertions, 0 deletions