Re; MTD (2) Block Driver broken

Gareth Bult gareth at
Tue Mar 8 05:33:31 EST 2005


would make a lot of sense.

At the end of the day and at the moment, I'm probably the only one using
the new driver so it's really not an issue .. I was really just talking
about "good form" when releasing updates ..


On Mon, 2005-03-07 at 23:42 +0100, Jörn Engel wrote:
> On Mon, 7 March 2005 22:20:38 +0000, Gareth Bult wrote:
> > 
> > > The old driver also got the interface wrong.  In your example, with
> > > just a single device to use, it doesn't matter.  But once you deal
> > > with several devices, the old variant really sucks.  That is why I
> > > changed it (and why I renamed the driver).
> > 
> > If you were to change the parameter name back to "device", it would be
> > compatible with the old driver. (pretty much) Hence you'd not need to
> > change the name (?)
> That would work for 99% of all users - those that only use a single
> device and no other parameters like erase size.  For the remaining 1%,
> I don't want to break anything, so the different name should remain.
> What I could do is introduce a new config option, like
> CONFIG_RENAME_BLOCK2MTD_TO_BLKMTD.  With the option set, the driver
> also accepts the "device" parameter and the kernel module is renamed.
> Would this work for you?
> Jörn
-- - promoting open source software in the UK
"If you have an apple and I have an apple and we exchange apples then
you and I will still each have one apple. But if you have an idea and I
have an idea and we exchange these ideas, then each of us will have two
ideas." - George Bernard Shaw

More information about the linux-mtd mailing list