|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Message-ID: <CDF99E351003D311A8B0009027457F1403BF93BC@ausxmrr501.us.dell.com> From: Matt_Domsch@Dell.com To: gibbs@plutotech.com, langa2@kph.uni-mainz.de Cc: sralston@ra.ks.lsil.com, linux-scsi@vger.rutgers.edu Date: Mon, 31 Jul 2000 19:05:06 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" I submitted a patch a couple weeks ago that sets the SDpnt->online=FALSE if the peripheral qualifier returned with a value 1 (device not physically connected). This just avoids the READ_CAPACITY inquiry and resulting error. As Justin suggests, the SCSI layer could take it to mean that a device won't be connected on that LUN, so it shouldn't attach to that device, and then later if a physical device IS connected, then use the scsi-add-single-device mechanism to bind it to a device name. int scan_scsis_single() ... if (((scsi_result[0] >> 5) & 7) == 1) SDpnt->online = FALSE; else SDpnt->online = TRUE; ... -Matt > -----Original Message----- > From: Justin T. Gibbs [mailto:gibbs@plutotech.com] > Sent: Monday, July 31, 2000 6:10 PM > To: Michael Lang A2 > Cc: Steve Ralston; linux-scsi > Subject: Re: Problem w/ recent scsi_scan changes > > Does Linux look at the content of the inquiry data to determine if > the Lun really is supported before attaching to it? Linux should only > attach if the lun qualifier is 0 (top 3 bits in byte 0 of inquiry > response). > > -- > Justin > > > - > To unsubscribe from this list: send the line "unsubscribe > linux-scsi" in > the body of a message to majordomo@vger.rutgers.edu > - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.rutgers.edu
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |