ramdisk

Hi all,

I would like to know how can I choose the RAM area is going to be used to load my ramdisk.

That's to say, in next boot capture we can see following line:
Loading Ramdisk to 0f33f000, end 0f9bcd1f

This is a RAM position (I have a 256 MB from 0x0) that I would like to change to a smaller one.

I am generating the ramdisk file with ltib so maybe I am losing something.

Bytes transferred = 71316 (11694 hex)

## Booting image at 00400000 ...
   Image Name:   Linux-2.6.24.6
   Created:      2011-03-15  14:17:51 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1815014 Bytes =  1.7 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

## Loading RAMDisk Image at 01000000 ...
   Image Name:   uboot ext2 ramdisk rootfs
   Created:      2011-03-15  14:20:13 UTC
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    6806815 Bytes =  6.5 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Booting using the fdt at 0x600000
   Loading Ramdisk to 0f33f000, end 0f9bcd1f ... OK
....
kernel messages

Thanks¡
pd:I am working with freescale ltib over an ads5121 based board (MPC5121e).

Sorry,

Ok, It semms setting initrd_high in u-boot I choose the max ram position.

I have another problem now when kernel tries to mount the filesystem:

[   90.959931] RAMDISK: Compressed image found at block 0
[   93.162656] RAMDISK: incomplete write (-28 != 32768) 33554432
[   93.715014] VFS: Mounted root (ext2 filesystem).
[   93.719726] Freeing unused kernel memory: 180k init
[   93.725405] attempt to access beyond end of device
[   93.730180] ram0: rw=0, want=72108, limit=65536
[   93.734977] attempt to access beyond end of device
[   93.739942] ram0: rw=0, want=73238, limit=65536
[   93.744490] Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
[   93.752801] Rebooting in 1 seconds..<0>System Halted, OK to turn off power

It must me related with some kernel ramdisk configuration. The mine are:

ram disks = 1
ramdisksize = 32 MB
blocksize = 1024

My resulting ramdisk.gz.uboot has only 6.5 MB so I don't know exactly the meaning of the previous kernel variable ramdisksize

More study for myself is needed

Any clue is appreciated

Regards,

Hi again¡

Problem solved, I had forgot set ramdisk_size uboot varable¡