mtd partitions on Sharp Zaurus

[Albert Rybalkin]

Thanks alot to all who replied and answered my questions, I really
appreciate your help. 

> 
> The latest kernel releases include proper read/write mtd flash drivers
> but incomplete partition information imho. jffs2 will work with an
> alternate kernel. The OpenZaurus project is configured to use jffs2
> instead of cramfs. 
> 

Doh. Don't know how I missed OpenZaurus, sorry... Just downloaded their
initrd and it's jffs2, indeed!
About missing partition information... Since the zaurus partition
info ("name",size, offset) is known, do you think it could be possible
to add it to some map driver? I saw your patch dated January 2002 at 
http://opensource.lineo.com/~timr/zaurus
but linux/drivers/mtd/maps/sa1100-flash.c v 1.7 does not seem to have any
mentioning of coolio partitions. Was it removed from kernel source or
moved along to other place? 

> The bootloader used on the Zaurus is a modified version of Angel. It
> uses multiple partitions as described on: 
> 
> http://www.btinternet.com/~p.flinders/sl-5000d/romimage-layout.html 
> 
> 128k - angel
> 128k - cf updater
> 512k - diagnostics
> 1M - kernel
> 14M+128k - root filesystem
> 128k - partition info 
> 
> It would be a fairly simple matter to convert that over to: 
> 
> 128k - blob (including CF updater, diagnostics, and partition table)
> 16M-128k - rootfs (including kernel and modules) 
> 

Ok, so /dev/mtdblock0 is "Angel" and /dev/mtdblock4 is initrd?
If I'll make my own jffs2 version of initrd and flash it in place
of Sharp's cramfs, does it mean that it could be mounted on
/dev/mtdblock4 ? Or am I missing the point? 

> 
> Ask your Sharp reps for this feature if you are interested in fitting
> more data in the internal flash. 
> 

It sure would be nice to get rid of small partitions and save some space.
I'll ask somebody from Sharp when I get a chance. Can you please give
me more details (email is ok) on what you need from sharp to
make it happen?
Thanks,
 -albertr