In message 20040528052946.GJ3369@pengutronix.de you wrote:
## Booting image at 50040000 ... Image Name: Linux Kernel Image Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 707679 Bytes = 691.1 kB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading Ramdisk Image at 50160000 ... Image Name: Ram Disk Image Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 2795019 Bytes = 2.7 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK
Any reason why you use an initrd on an embedded system? initrds are for mainstream distributions who want to completely modularize their kernels, and I doubt that this is what you have in mind ;)
C'mon Robert. You know very well that it is very common to put the root filesystem on a ramdisk in embedded systems. It has a couple of advantages (and disadvantages, too).
Are you sure your memory map is ok? I don't know the IXPs, but on ARM you normally have flash at 0x0, so loading the Linux kernel to 0x0+0x8000 and loading the initrd to 0x0 is probably not the best idea.
You are right about the kernel addresses being probably much too low; but Load Address and Entry Point don't play a role for the ramdisk.
Best regards,
Wolfgang Denk