[PATCH] MTD Maps driver for Sharp LH7a40x

Thomas Gleixner tglx at linutronix.de
Fri Jun 18 20:16:29 EDT 2004


On Saturday 19 June 2004 02:05, Jun Sun wrote:
> How about just using physmap mapping driver and keep all your
> board specific stuff to your board directory?   See
> include/linux/mtd/physmap.h for more details.

Thanks for jumping in. That's what I was trying to point out. 

In fact most of the board drivers in drivers/mtd/maps could / should go away. 
The reason to have one is crappy hardware, unusual chip constellations or 
other anomalities.

The common case can just be solved by using the physmap driver and the command 
line partition parser. Maybe we should think about an extension to physmap so 
the board support code can supply an appropriate partitioning scheme along 
with the chip description. 

I was thinking about simliar support for the NAND driver too, but there it 
turns out that the anomalities are given per design, although it should not 
be an unsolvable problem.

From slash dot org
"When customers are visiting, engineers are not allowed to wear ties. 
That way the customer can tell who is the engineer and who is the 
salesman (and therefore whom to believe.). Ties cut off blood flow 
to the brain, making it easier for the salesmen to do their jobs." 
linutronix - competence in embedded & realtime linux
mail: tglx at linutronix.de

More information about the linux-mtd mailing list