It seems Francis Jordan wrote:
> Yes, HDD on the primary, CD-ROM on the secondary controller. This is a
> notebook I'm talking about, so I haven't tried any other CD-ROM drives.
> If it doesn't respond at all, then how do you get all the other
> information, such as supported read types, speed, etc? Perhaps there is
> some other way of making this particular CD-ROM drive generate an
> interrupt? Of course, it's just a minor annoyance (and otherwise I'm
> very pleased with the driver's performance - many thanks to SOS), but if
> the new ATA driver were to eventually replace the old one, it's not a
> bad idea to try and get rid of as many silly error messages as possible.
Hmm try the patch below so we can tell what command it is failing on..
> Is there just one standard that all ATAPI CD-ROM drives must comply
> with, or can there be variations? I apologize if this is a silly
> question.
There is several versions of the ATAPI standard, but they are all
pretty vague, there is LOTS of room for vendors to "improve" thier
devices :(
Index: ata-all.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v
retrieving revision 1.16
diff -u -r1.16 ata-all.c
--- ata-all.c 1999/08/06 17:39:37 1.16
+++ ata-all.c 1999/08/11 07:00:09
@@ -693,7 +693,8 @@
scp->active = ATA_WAIT_INTR;
outb(scp->ioaddr + ATA_CMD, command);
if (tsleep((caddr_t)scp, PRIBIO, "atacmd", 500)) {
- printf("ata_command: timeout waiting for interrupt\n");
+ printf("ata_command: timeout waiting for interrupt (cmd=0x%02x)\n,
+ command");
scp->active = ATA_IDLE;
return -1;
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
