[PATCH] [MTD] NAND: add ts7xxx driver

Alexander Clouter alex at digriz.org.uk
Sun Feb 8 05:52:26 EST 2009


Hi,

* Alexander Clouter <alex at digriz.org.uk> [2009-02-08 10:39:04+0000]:
> 
> * Lennert Buytenhek <buytenh at wantstofly.org> [2009-02-08 11:21:47+0100]:
> > 
> > On Sun, Feb 08, 2009 at 08:59:19AM +0000, Alexander Clouter wrote:
> > >
> > > This patch adds support for the NAND found in Technologic Systems ARM
> > > boards[1].  The platform specific parts (IO address and parititoning
> > > schemes) have been moved into platform specific files whilst the driver
> > > it's self can be used as a complete replacement for the ts7250 NAND
> > > driver.
> > 
> > Why don't you morph the ts7250 into the form you want instead of adding
> > a parallel driver for the same thing?
> >
> 
> [snipped rant]
> 
> The driver I threw together makes a rather radical change to put all the 
> partitioning and iomem resources ranges back into the platform specific 
> code where they belong.  It was just easier to start clean, plus I 
> learnt a good deal about the MTD subsystem in the process, although 
> that's not a good reason for submission I know.
> 
Attached is the kind of change that affects the platform code.  
Meanwhile if I was to morph the ts7250 driver my first step would be to 
trim a huge chunk of the platform specific code that's in the NAND 
driver and then at the same time get the ARM platform driver amended 
otherwise you end up with a NAND less board.

It's been hard enough to submit my TS-7800 patches and break them up so 
the different subsystems gracefully get added.  To modify the existing 
ts7250 driver I would have to take on the tinkering and submission 
cycles with the TS-72[056]0 (when I don't own one) too.  As I so far 
have gotten zero feedback[1] from the community this seems to me the 
*only* way I can work on my patches with a view for upstream submission.

This way, with a separate driver, when things finally/if-ever get 
accepted nothing breaks.  I think the changes also being made are easier 
for someone

If you know of a way that the MTD folk are willing to tinker with the 
ARM subsystem code and vice versa (last time I was told by the ARM 
people to break up my MTD stuff and submit it to you guys separately) 
then I'm listening.

I'm stuck in a rut and it really is wearing me down...I'm not even a 
embedded developer, just a network packet pushing perl monkey who just 
wants to get his router working :-/

Cheers

[1] and I still do not understand why in the ts7000 mailing list there 
	is all this work on a seperate patch set for ts72[560]0 support 
	when they apparently do not have a NAND driver even?  Any ideas?



More information about the linux-mtd mailing list