Alan Cox wrote:
The old drivers/ide code uses much longer delays than the spec for some
ATAPI commands, and it looks as if there is a good reason for doing
so ...
FWIW, the code that ATADRVR (http://www.ata-atapi.com/) uses to issue
commands does something like
write Command register to start command
if (device == ATAPI) # i.e. not ATA
delay(150 msec)
pound Status / AltStatus, kick DMA engine, whatever else
ATADRVR is open code (for an MS-DOS-level driver), and really worth a
read. Between ATADRVR and drivers/ide, you get a pretty good idea about
what __field experience__ has shown is needed for ATAPI devices.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
