I have some questions about the bootldr btflash.c
and mtd sa1100-flash.c. I am using a Phase 5 Assabet,
and have BIG_KERNEL set.
First, here are the relevant sections of code:
(btflash.c)
{ "bootldr", 0x00000000, 0x00040000, LFR_PATCH_BOOTLDR },
{ "params", 0x00040000, 0x00040000, 0 },
{ "kernel", 0x00080000, 0x000c0000, LFR_KERNEL },
{ "ramdisk", 0x00140000, 0x006c0000, LFR_SIZE_PREFIX },
{ "usercode", 0x00140000, 0x006c0000, 0 },
{ "jffs", 0x00800000, 0x00800000, LFR_ERASEALL }
(sa1100-flash.c)
{
name: "bootloader",
size: 0x00040000,
offset: 0,
mask_flags: MTD_WRITEABLE
},{
name: "bootloader params",
size: 0x00040000,
offset: 0x00040000,
},{
name: "kernel",
size: 0x000c0000,
offset: 0x00080000,
},{
name: "ramdisk",
size: 0x006c0000,
offset: 0x00140000,
},{
name: "jffs",
size: 0x00800000,
offset: 0x00800000
}
1. Does there have to be a corresponding partition
entry in sa1100-flash.c for every partition entry in
btflash.c (many of which are aliases of same area, or overlap).
I have only specfied mtd partitions that I will use (see above).
IS this correct? Also, are there any special constraints on JFFS
location: is it OK for jffs to start at 0x00800000?
2. Are the mtd partition names specified in sa1100-flash.c
the ones I have to use in the linuxargs param in bootldr, or
are they aliases for mtdblock0,1,2 ... ??
ie if I want to set root to my jffs image (which I made from a
ramdisk), do I set linuxargs to:
linuxargs= noinitrd root=/dev/mtdblock4 init=/linuxrc console=ttySA0
or
linuxargs= noinitrd root=/dev/jffs init=/linuxrc console=ttySA0
3. Finally, is there anything in my partition descriptions that
could cause problems. I have modified the original srcs, changing
the start address and length of jffs partition. Previously my kernel
would load successfully with bootldr, but now the transfer terminates
at 665K.
4. I am using JDs 17 Apr bootldr patch on handhelds src of same
period.
Thanks to anyone that can help.
Tim
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
