David.Woodhouse at mvhi.com
Thu Oct 21 03:52:43 EDT 1999
mferrell at nortelnetworks.com said:
> And that's it. It opens the device for a short duration of time ..
> but nothing comes forth. I tried all sortsa fun with noluck. Any
> ideas, suggestions, large bat's to beat the system about the head
Hmmm. To test your driver itself, use the character devices, which are what
/dev/mtd0 ought to be.
When you're sure that's OK, you ought just to be able to load the mtdblock
device (after your driver) and use /dev/mtdblock0 too. There may be bugs in
the mtdblock code, however.
Can you trace and send me the oops that you get if you load mtd, pmc551, then
mtdblock in that order?
Also, it's worth checking that the mtdblock code actually sets the size of the
block device. The kernel might be refusing to pass on any read() requests
because we've left the device size set to zero.
---- ---- ----
David Woodhouse David.Woodhouse at mvhi.com Office: (+44) 1223 810302
Project Leader, Process Information Systems Mobile: (+44) 7976 658355
Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK.
finger dwmw2 at ferret.lmh.ox.ac.uk for PGP key.
To unsubscribe, send "unsubscribe mtd" to majordomo at imladris.demon.co.uk
More information about the linux-mtd