mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Turk" <r.turk@chello.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: PATCH: scsi_scan.c: emulate windows behavior
Date: Tue, 13 Nov 2001 20:49:09 +0100	[thread overview]
Message-ID: <9srtm6$8hf$1@ncc1701.cistron.net> (raw)
In-Reply-To: <20011113102106.A23110@one-eyed-alien.net>

"Matthew Dharm" <mdharm-kernel@one-eyed-alien.net> wrote in message
news:cistron.20011113102106.A23110@one-eyed-alien.net...

>Attached is a one-liner patch to scsi_scan.c, which changes the length of
>the INQUIRY data request from 255 bytes to 36 bytes.  This subtle change
>makes Linux act more like Win/MacOS and other popular OSes, and reduces
>incompatibility with a broad range of out-of-spec devices that will simply
>die if asked for more than the required minimum of 36 bytes.

>Matt

Matt,

Many devices have useful information in the bytes beyond 36. Media changers from
various vendors are starting to use byte 55 bit 0 to flag if a barcode scanner
is present. Other devices have revision levels and/or serial numbers there.

Getting more than 36 bytes should not be a problem for any device. The root
problem seems to be that 255 is an odd number. On Wide-SCSI, a lot of devices
have difficulty handling odd byte counts as they have to use additional
messaging to flag the residue in the last 16-bit transfer. Also, the IDE-SCSI
layer has trouble, as the IDE spec doesn't allow odd byte transfers at all. I've
experienced issues with IDE devices that had to have their firmware patched just
to deal with the Linux odd-byte request. Maybe a better change would be to use
64 or 128 byte requests. Your thoughts?

Rob





  reply	other threads:[~2001-11-13 19:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 18:21 Matthew Dharm
2001-11-13 19:49 ` Rob Turk [this message]
2001-11-13 20:08   ` Matthew Dharm
2001-11-13 18:02     ` Gérard Roudier
2001-11-13 23:26     ` Alan Cox
2001-11-14  1:44       ` Matthew Dharm
2001-11-14  0:45   ` Riley Williams
2001-11-13 22:52 ` Alan Cox

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='9srtm6$8hf$1@ncc1701.cistron.net' \
    --to=r.turk@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®