> Anyway, from my modest point of view, the u-boot flash memory model is
> too rigid. I would like a "linux" model like this:
> -----------
> | |-> [ MTD Driver ] -> Flash 1 (Nor)
> ---> flash operation --> | MTD Mux |-> [ MTD Driver ] -> Flash 2 (Nand)
> | |-> [ MTD Driver ] -> Flash n (XXX)
> -----------
>
I don't think it works that way in Linux. The devices you're
concatenating must be basically the same (both nor or nand,
same width, same sector size / OOB area size for NAND, etc ) . That's
what I understand after a quick read of the docs.
Yes, you're right. I just proposed a different architecture that is not implemented in U-boot :)
> MTD Mus is itself a MTD Driver. This infrastructure could be implemented
> using smart descriptor to keep the need callback.
>
You could easily do that, but you still need to have similar devices.
Anyway, we're talking about an embedded bootloader here, you put too
much stuff in it and it gets bigger than the actual application :-)