On 2010/08/18 12:04 AM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
> 
> In message <4c6b051a.5050...@dawes.za.net> you wrote:
>>
>> For some reason, the kernel didn't seem to think it had been given the
>> ramdisk parameter. At least, I get the following error message:
> 
> Where is the ramdisk located? Make sure it is loaded into RAM (not
> flash!).
> 
> Best regards,
> 
> Wolfgang Denk

Hi Wolfgang,

The ramdisk is located at ff9a0000 (in flash). Its image header
relocates it to 00800000:

>From the vendor u-boot:

## Loading Ramdisk Image at ff9a0000 ...
   Image Name:   Ramdisk
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5240600 Bytes =  5 MB
   Load Address: 00800000
   Entry Point:  00800000
   Verifying Checksum ... OK

And from mine:

DNS323B1> setenv verify no
DNS323B1> run bootcmd
## Booting kernel from Legacy Image at ff820000 ...
   Image Name:   Linux-2.6.12.6-arm1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1490204 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
## Loading init Ramdisk from Legacy Image at ff9a0000 ...
   Image Name:   Ramdisk
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5240600 Bytes = 5 MiB
   Load Address: 00800000
   Entry Point:  00800000
   Loading Kernel Image ... OK
OK

0x800000 is well within the 64MB that the device has.

Regards,

Rogan
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to