Hi Pavel,
I tend to load zImage *before* the ramdisk since it is easier
as the ramdisk image grows.
For example zImage at 0x0600000 and ramdisk.gz at 0x0800000
If you use a newer version of genextfs (I have 1.4-rc1 with Ubuntu)
it will happily generate images larger than 8M.
You might also want to check your kernel configuration
to ensure that it allows ramdisks >8M
Cheers,
Steve
On 30/07/2007, at 10:49 PM, Doug Kehn wrote:
Hi Pavel,
--- Pavel wrote:
Hello.
I have an IXP425 dev. board with 64M RAM and 16M
Flash.
Redboot doing:
1. zImage - 0x1600000
2. ramdisk.gz - 0x0800000
3. go 0x1600000
My ramdisk size = 8192. And all works ok.
But i need to increase ramdisk to 16M (or to 12M).
But there is a problem: 0x1600000 - 0x0800000 =
0x0E00000 (14M).
ramdisk.gz ~ 2M,
what can be maximum size of uncompressed ramdisk?
I think, than in my situatition the sum of ramdisk
and ramdisk.gz can't be > 14M?
Where will be uncompressed ramdisk allocated?
Can i change it position?
You can look to see what the size of your Redboot is
and then load the kernel (zImage) just above it and
then load the ramdisk just above the kernel. Don't
forget to update the kernel command-line to point to
the new ramdisk location. For example, you could try
to load the kernel at 0x00030000 and the ramdisk at
0x00230000.
IIRC genext2fs will only generate ramdisks up to 8MB.
You may need to search for an update/patch.
Regards,
...doug
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
