[PATCH] OneNAND: Update OMAP OneNAND mapping using device driver model

[Kyungmin Park]

Hi

In previous way. we have to modify omap-onenand.c file itself. and it is
difficult to adapt another omap platform.

But each platform has some different partition configurations and
chip-select.

e.g., OSK use CS2 as OneNAND, But my custom board use CS3. 

So I move the partition information to each platform as NOR does

e.g., linux/arm/arch/mach-omap1/board-*.c

Now we only modify each platform configuation file.

Regrads,

Kyungmin Park

> -----Original Message-----
> From: Bernhard Priewasser [mailto:priewasser at gmail.com] 
> Sent: Wednesday, August 31, 2005 11:22 PM
> To: kyungmin.park at samsung.com
> Cc: linux-mtd at lists.infradead.org
> Subject: Re: [PATCH] OneNAND: Update OMAP OneNAND mapping 
> using device driver model
> 
> Hi Kyungmin,
> 
> what are the advantages in opposite to the existing way, e.g. (why) 
> shall I use it for "porting" the OneNAND stuff to another board?
> 
> Regards,
> Bernhard
> 
>