diff options
| author | Maxime Ripard <maxime.ripard@free-electrons.com> | 2015-04-24 12:53:12 +0200 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2015-05-08 17:24:17 -0400 |
| commit | 87f02d5aeef53bc2028b433a4c02ef2b2eea8c87 (patch) | |
| tree | d1b88574aefe8312b3aaf7ac9b0a07962f6b67e8 /board/BuR/common/common.c | |
| parent | a67da8fd67911ef87f296622b3758d04b1b76e2c (diff) | |
| download | u-boot-imx-87f02d5aeef53bc2028b433a4c02ef2b2eea8c87.zip u-boot-imx-87f02d5aeef53bc2028b433a4c02ef2b2eea8c87.tar.gz u-boot-imx-87f02d5aeef53bc2028b433a4c02ef2b2eea8c87.tar.bz2 | |
image: android: handle default kernel address
The two tools that create android boot images, mkbootimg and the fastboot
client, set the kernel address by default to 0x10008000.
U-boot always honors this field, and will try to relocate the kernel to
whatever value is set in the header, which won't be mapped to the actual RAM on
most platforms, resulting in the kernel obviously not booting.
All the targets in U-Boot right now will download the android boot image to
CONFIG_SYS_LOAD_ADDR, which means that it will already have been downloaded to
some location that is suitable for execution.
In order to have the kernel booting even with the default boot image kernel
address, if that address is used, just execute the kernel where it is.
Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Diffstat (limited to 'board/BuR/common/common.c')
0 files changed, 0 insertions, 0 deletions