[new uImage] Don't pass kdb to ramdisk_high since we may not have one

We don't actually need the kdb param as we are just using it to get
bd->bi_memsize which we can get from gd->bd->bi_memsize.  Also, if we
boot via OF we might not actually fill out a kdb.

Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Acked-by: Marian Balakowicz <m8@semihalf.com>
This commit is contained in:
Kumar Gala
2008-02-27 21:51:43 -06:00
committed by Marian Balakowicz
parent 4efbe9dbb1
commit a6612bdfe7
4 changed files with 7 additions and 10 deletions

View File

@@ -100,8 +100,7 @@ void do_bootm_linux(cmd_tbl_t * cmdtp, int flag,
rd_len = rd_data_end - rd_data_start;
alloc_current = ramdisk_high (alloc_current, rd_data_start, rd_len,
kbd, sp_limit, get_sp (),
&initrd_start, &initrd_end);
sp_limit, get_sp (), &initrd_start, &initrd_end);
debug("## Transferring control to Linux (at address %08lx) ...\n",
(ulong) kernel);