diff options
author | Yuri Tikhonov <yur@emcraft.com> | 2008-11-14 16:19:19 +0300 |
---|---|---|
committer | Stefan Roese <sr@denx.de> | 2008-11-21 11:08:02 +0100 |
commit | 1a6a00dcc5bdfc6e9b4b00f39c1f583a7f96fc7f (patch) | |
tree | 753acad70f3c15d7be5d4fc1315fc5393a55e2c7 /doc | |
parent | ddf45cc758d394591fb9bcdcbe96530f733f2bce (diff) | |
download | u-boot-imx-1a6a00dcc5bdfc6e9b4b00f39c1f583a7f96fc7f.zip u-boot-imx-1a6a00dcc5bdfc6e9b4b00f39c1f583a7f96fc7f.tar.gz u-boot-imx-1a6a00dcc5bdfc6e9b4b00f39c1f583a7f96fc7f.tar.bz2 |
ppc4xx: katmai: Change default config
This patch enables support for EXT2, and increases the
CONFIG_SYS_BOOTMAPSZ size for the default configuration
of the katmai boards to use them as the RAID-reference
AMCC setups.
EXT2 enabling allows one to boot kernels from the EXT2
formatted Compact Flash cards.
CONFIG_SYS_BOOTMAPSZ increasing allows one to boot the
Linux kernels, which use PAGE_SIZE of 256KB. Otherwise,
the memory area with DTB file (which is placed at the
end of the bootmap area) will turn out to be overlapped
with the BSS segment of the 256KB kernel, and zeroed
in early_init() of Linux.
Actually, increasing of the bootmap size could be done
via setting of the bootm_size U-Boot variable, but it looks
like the current U-Boot implementation have some bootm_size-
related functionality lost. In many places through the U-Boot
code the CONFIG_SYS_BOOTMAPSZ definition is used directly
(instead of trying to read the corresponding value from the
environment). The same is truth for the boot_jump_linux()
function in lib_ppc/bootm.c, where U-Boot transfers control
to Linux passing the CONFIG_SYS_BOOTMAPSZ (not bootm_size)
value to the booting kernel.
Signed-off-by: Yuri Tikhonov <yur@emcraft.com>
Signed-off-by: Ilya Yanok <yanok@emcraft.com>
Signed-off-by: Stefan Roese <sr@denx.de>
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions