[PATCH] remove support for virtual blocks

Jörn Engel joern at wohnheim.fh-wedel.de
Mon Aug 29 06:07:22 EDT 2005

On Fri, 26 August 2005 15:12:29 -0500, Josh Boyer wrote:
> On Fri, 2005-08-26 at 12:25 +0200, Jörn Engel wrote:
> > Trivial patch.  Anyone complaining about this is free to write a
> > better one.  Can I commit?
> So now with this 1:1 mapping, a user is limited to using a 64 MiB chip
> if the physical block size is 32 KiB?  I know there are NAND chips out
> there that use such a block size and are larger than 64MiB.  Do we
> really want to stop supporting all of these devices?  


What we have right now is an ugly hack that causes random
incompatibilities.  And it happens to be that both summary and erase
count increase the chances of an incompatibility, so this hack
effectively blocks both patches from inclusion.

What we need is a decent design that works without incompatibilities.
And the design should define what's on the medium, _independently_ of
whatever goes on in memory.  Changing the format on the medium because
some struct now has an extra field is not an option.  Changing the
format because the medium moved from a 32bit to a 64bit machine is not
an option.

Problem is that code for the decent design doesn't exist yet.  I
personally prefer this patch to the current broken implementation, as
it increases the pressure to write the correct code.  If such code
doesn't show up in the near future, I'd be inclined to commit my


They laughed at Galileo.  They laughed at Copernicus.  They laughed at
Columbus. But remember, they also laughed at Bozo the Clown.
-- unknown

More information about the linux-mtd mailing list