unts it if I don't pass
any arguments on the command line about its memory location? That's what
I don't understand! Also, I thought it is necessary to use mkimage not only
for the kernel image but also for the initrd for being able to be used by
U-boot, but as it seems it's not!
Hi all,
I have a query regarding the boot of an initrd with U-boot. ASAIK,
ramdisk.gz should be converted to a type supported by U-boot with the use
of mkimage tool (with a -T ramdisk switch). Also, the "bootm" command should
be invoked by passing the address of uImage first and then the addre
Thanks for the reply.
If menuconfig and Kconfig are not supported yet, is there a way to configure
my U-boot version?
From: Ben Warren [mailto:biggerbadder...@gmail.com]
Sent: 25 November 2009 15:33
To: Ioannis Kyriakopoulos
Cc: u-boot@lists.denx.de
Subject: Re: [U-Boot] Unable to launch
Hi all,
I have downloaded the u-boot source and I am able to build it for my target
(beagleboard). However, I am not able to launch menuconfig. I know that
menuconfig works because I am able to launch it when I am building my Linux
kernel.
$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnue
4 matches
Mail list logo
