More comments

Alexander Larsson alex at
Sun Mar 12 07:20:10 EST 2000

Ok. I've worked some more with mtd now.

What is the reason for having the read and write ops not always read/write
the number of bytes you specify? (I guess that this is what the size_t
*retlen argument means.)

What concurrency assumptions does mtd make? Since the ops can sleep
(could be waiting for a sector erase to finish) there must be some kind of
locking. Who does the locking? What is "int *lock" in struct mtd? (and
shouldn't it be a semaphore or a spinlock?) Which operations can be called
from interrupt-context?

/ Alex

To unsubscribe, send "unsubscribe mtd" to majordomo at

More information about the linux-mtd mailing list