I'm getting ready to make some changes to the ide-floppy driver (to support
dynamic media change notification), and after spending a few days reviewing
most of the IDE driver code (ide, ide-disk, ide-cd, ide-floppy and
ide-probe), I think I've got a good handle on what needs to be done.
However, since what I need to do involves sending some ATA (not ATAPI)
commands to the drive, that will add some complexity to the ide-floppy
driver. I'm not opposed to that, but it appears that many of the other
drivers (ide, ide-disk and ide-cd) already have code to send an ATA command
(writing to the registers), and interrupt handlers to handle sending or
receiving the buffer(s) of data that the command wants to transfer.
Is this the way it is intended to be, with this code duplicated in multiple
subdrivers? The sheer complexity of the DMA interface would make me think it
would be far better for this "infrastructure" stuff to all be in ide.c, and
just be used by the subdrivers. I can certainly make yet another copy of the
code for the few commands that ide-floppy will need to be able to issue, but
before I went about that I thought I'd see if there was a better plan...
Thanks for your attention.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 23 2001 - 21:00:35 EST