RE: Rio filesystem

Jeremy Fitzhardinge (jeremy@goop.org)
Thu, 21 Oct 1999 18:51:02 -0700 (PDT)


On 21-Oct-99 Steven_Hazel@trilogy.com wrote:
> - The Rio expects to communicate in blocks of 528 (512 + 16) bytes.
> Since Linux expects device driver block sizes to be powers of 2, should
> I just be using 1024-byte blocks and trashing the extra space above
> 528? Or is there a better way to do it?

The block device layer certainly likes to talk to devices with 2^n blocks
sizes, but you shouldn't need to worry about that. If you're writing a
filesystem interface for the Rio, then it should be an NFS-like filesystem
rather than a ext2-like filesystem; that is, it isn't associated with a block
device, and isn't layered on the buffer cache. If you want to use the page
cache, then you can map the Rio blocks into cache pages in any way you like.

> - How should I be handling system-speed-independant timings in kernel
> code (or if your answer is RTFM, where's the FM)?

What sort of stuff? Do you mean fiddling with printer port control bits? It
depends on what sort of accuracy you need, and what kinds of delays. If its
just a few microseconds here and there you can use udelay; if you need to do
things like "wait at least 2ms" then you can use a blocking sleep.

J

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/