[U-Boot-Users] M-Systems Disk on Chip and U-boot

[Udi Finkelstein <udif@udif.com>]

Herb Radford wrote:
> We're looking at using a DoC on our next product and I was wondering how 
> the drivers (obviously supplied by M-Systems) are merged into U-Boot code?

I just began working on improving DoC support (for the RBC823 board), 
but I had a few questions. Since you have mentioned the subject of DoC I 
think its a good time to raise them here:

If I understand correctly, the Linux MTD drivers has two layers. The 
lower device level handles actual device access, while the upper layer 
(NFTL, etc.) handles wear leveling.

1. If I undersnatd correctly, u-boot only implemented the lower level, 
right? no NFTL driver is currently in U-boot.

2. Is the Linux MTD NFTL driver compatible (in terms of disk format) 
with the M-sys TrueFFS driver ? can I use the same device with both 
software stacks without corrupting it?

3. Which layer handles ECC correction?

4. What good is the current u-boot support if it has no NFTL, and hence 
no wear leveling? I assume I can't just map the FAT commands over it 
without NFTL, as it won't be reable (if written over NFTL).

5. I understand the DoC has 2 partitions (at least the 8M models) - a 
binary partition and the normal partition. what is the difference 
between them?

I plan adaptin gthe NFTL layer from the linux-MTD project into u-boot, 
and add support for the FAT commands.

thanks,
Udi