summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjoerg <joerg@FreeBSD.org>2000-12-04 20:16:06 +0000
committerjoerg <joerg@FreeBSD.org>2000-12-04 20:16:06 +0000
commitf2e5184027227edebf7519183f99bc3f8b96dc64 (patch)
tree4e88619ed5ee83928904be2b465b94501519ed3a
parentbb34593642604d426a985e6c15215571e0e5ba5a (diff)
downloadFreeBSD-src-f2e5184027227edebf7519183f99bc3f8b96dc64.zip
FreeBSD-src-f2e5184027227edebf7519183f99bc3f8b96dc64.tar.gz
Turn off the load_eject bit in cdstartunit(). It causes an `Invalid
field in CDB' error when attempting to start a caddy-type CD drive, since those drives apparently in general refuse to load a medium. Since we never advertised the feature to load the medium upon calling cdstartunit() (i. e. upon receipt of a CDIOCSTART ioctl command), nobody should have relied on it. Besides, nobody noticed so far at all that this command is failing for caddy-type drives... Only few applications seem to use it at all (among them is workman, which made me notice it). Reviewed by: ken
-rw-r--r--sys/cam/scsi/scsi_cd.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/cam/scsi/scsi_cd.c b/sys/cam/scsi/scsi_cd.c
index 662327e..d140f9b 100644
--- a/sys/cam/scsi/scsi_cd.c
+++ b/sys/cam/scsi/scsi_cd.c
@@ -3038,7 +3038,7 @@ cdstartunit(struct cam_periph *periph)
/* cbfcnp */ cddone,
/* tag_action */ MSG_SIMPLE_Q_TAG,
/* start */ TRUE,
- /* load_eject */ TRUE,
+ /* load_eject */ FALSE,
/* immediate */ FALSE,
/* sense_len */ SSD_FULL_SIZE,
/* timeout */ 50000);
OpenPOWER on IntegriCloud