Re: [linuxdc-dev] VMU driver (Better maple)

[M. R. B. <mr...@0x...>]

* Fredrik Hubinette <hu...@hu...> on Sat, Jan 26, 2002:

> > > In particular, the mtd subsystem seems to use driver api
> > > which writes one byte at a time, which is something
> > > I would really really like to avoid in a VMU driver.
> > >=20
> >=20
> > Where did you see this?  That MTD couldn't handle block devices?
>=20
> Well, I might be reading the whole thing wrong, but as I understand
> the code, it provides both char and block devices for each mtd device.
> However, the mtd map handler has a byte-based interface which seems
> like a lot of extra work to implement. This may however be incorrect.
> I will do some more reading, but maybe someone more knowledge can save
> me some trouble by pointing me in the right direction?
>=20

I remember now.  Paul's idea was to read/write from the VMU in blocks, but
provide the byte-interface for the currently held block.  If you need byte
512, you'd have to read in that block in order to get to it.  Sound sane?

It's complicated.  I'd wait for his answer, or see if any other MTD devices
do anything similiar.

M. R.