diff options
author | Michael Walle <michael@walle.cc> | 2015-02-08 20:06:07 +0100 |
---|---|---|
committer | Luka Perkov <luka.perkov@sartura.hr> | 2015-02-12 15:28:02 +0100 |
commit | 4fe49d7becc2dfb7288f8b265e0976428b64323c (patch) | |
tree | 4df8167b5af72191c88af7e07844444c9958d001 /lib/Kconfig | |
parent | 145df6fe2a5897cfda0ca2992d0e08cdb9cc0cde (diff) | |
download | u-boot-imx-4fe49d7becc2dfb7288f8b265e0976428b64323c.zip u-boot-imx-4fe49d7becc2dfb7288f8b265e0976428b64323c.tar.gz u-boot-imx-4fe49d7becc2dfb7288f8b265e0976428b64323c.tar.bz2 |
lsxl: switch from bootm to bootz for boot commands
Use the bootz command to load zImages in case of any new boot scripts. Only
the legacy one will still use bootm. Apart form the fact, that this will
simplify the image generation process, it saves one copy of the kernel
image: Common practice is to generate an uImage with a loading address of
0x8000. This uImage contains a compressed zImage, which will unpack the
kernel image to the beginning of the RAM. But because there is already the
compressed image the uncompressor first relocates the compressed image to a
higher location. The load address is encoded into the uImage which is
generated by the distributions and thus cannot be easily changed. By using
the bootz command we can load the compressed image to a higher memory
address and the decompressor doesn't have to reloacte the image.
Signed-off-by: Michael Walle <michael@walle.cc>
Diffstat (limited to 'lib/Kconfig')
0 files changed, 0 insertions, 0 deletions