From: Andries Brouwer <aebr@win.tue.nl>
To: Rob Turk <r.turk@chello.nl>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MODE SENSE in sd.c; sddr09.c
Date: Mon, 2 Sep 2002 14:38:09 +0200 [thread overview]
Message-ID: <20020902123809.GA9286@win.tue.nl> (raw)
In-Reply-To: <akvg26$7nt$1@ncc1701.cistron.net>
On Mon, Sep 02, 2002 at 01:00:39PM +0200, Rob Turk wrote:
> > The patch below first separates out the MODE SENSE call,
> > and then tries it three times: on all pages (3F), only the first
> > four bytes; on the vendor page (0), only the first four bytes;
> > on all pages (3F), 255 bytes.
>
> Would it be possible to move away from using 'standard' 255 bytes? Many SCSI
> device don't like requests for odd byte counts on 16-bit SCSI busses, and
> IDE isn't too crazy about it either. How about asking for 254 instead??
Well, as you can see I did move away from the 255. I ask for 4 bytes.
Only if that fails do I fall back on what we do today.
Andries
prev parent reply other threads:[~2002-09-02 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 0:41 [PATCH] MODE SENSE in sd.c; sddr09.c Andries.Brouwer
2002-09-02 11:00 ` Rob Turk
2002-09-02 12:38 ` Andries Brouwer [this message]
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=20020902123809.GA9286@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=r.turk@chello.nl \
/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