From: Luben Tuikov <luben@splentec.com>
To: Matthew Dharm <mdharm-scsi@one-eyed-alien.net>
Cc: Andries.Brouwer@cwi.nl, stern@rowland.harvard.edu,
linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: inquiry in scsi_scan.c
Date: Mon, 06 Jan 2003 15:49:08 -0500 [thread overview]
Message-ID: <3E19EBC4.6000601@splentec.com> (raw)
In-Reply-To: 20030106112259.B13916@one-eyed-alien.net
Matthew Dharm wrote:
>
> Perhaps the "best" fix here is to simply make scsi_scan.c only send 36 byte
> inquiry requests if the bus is 'emulated'. That would solve a world of
> problems....
When scsi_scan.c does it's own scanning for SCSI Core, maybe it's best to
ignore 36 < INQUIRY_DATA_LEN < 57, since this is just vendor specific
data and SCSI Core is not interested in it.
In descriptive-C this looks like this:
</issue a 36 byte buffer INQUIRY/>
</now dissect:/>
int bytes_got = max(bytes_requested - cmd->resid, 0);
if (31 < buffer[4] && buffer[4] < 52) {
/* we don't care, do not issue another INQUIRY */
else if (buffer[4] >= 52) {
bytes_requested = 5+buffer[4];
/* issue another INQUIRY to get the additional flags, */
/* plus any version descriptors if available */
</insert code here/>
bytes_got = max(bytes_requested - cmd->resid, 0);
}
if (bytes_got != buffer[4]+5) {
/* let's rely on the transport to have correctly set */
/* cmd->resid and report a broken device server */
</insert code here/>
}
/* Now we rely on bytes_got */
</rest of scanning code/>
--
Luben
next prev parent reply other threads:[~2003-01-06 20:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 19:18 Re: inquiry in scsi_scan.c Andries.Brouwer
2003-01-06 19:22 ` Matthew Dharm
2003-01-06 20:49 ` Luben Tuikov [this message]
2003-01-06 21:03 ` [linux-usb-devel] " James Bottomley
2003-01-06 21:05 ` Matthew Dharm
2003-01-06 21:16 ` [linux-usb-devel] " Luben Tuikov
2003-01-06 22:07 ` Doug Ledford
2003-01-06 22:10 ` Doug Ledford
2003-01-06 22:23 ` Doug Ledford
2003-01-07 0:46 ` Matthew Dharm
2003-01-07 3:42 ` Doug Ledford
2003-01-07 15:15 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2003-01-05 13:07 Andries.Brouwer
2003-01-06 15:03 ` [linux-usb-devel] " Alan Stern
2003-01-06 16:43 ` Luben Tuikov
2003-01-06 18:54 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E19EBC4.6000601@splentec.com \
--to=luben@splentec.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox