From: Torben Mathiasen <torben@kernel.dk>
To: Elizabeth Morris-Baker <eamb@liu.fafner.com>
Cc: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
chen xiangping <chen_xiangping@emc.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: scsi init problem in 2.4.0-test10?
Date: Fri, 3 Nov 2000 00:50:34 +0100 [thread overview]
Message-ID: <20001103005034.C1353@torben> (raw)
In-Reply-To: <20001102145320.A27745@one-eyed-alien.net> <200011022245.QAA08323@liu.fafner.com>
In-Reply-To: <200011022245.QAA08323@liu.fafner.com>; from eamb@liu.fafner.com on Thu, Nov 02, 2000 at 04:45:25PM -0600
The SCSI spec says that INQUIRY and not
TUR + INQUIRY is the way to go, but maybe we
should make it a compile time option for buggy
drives.
On Thu, Nov 02 2000, Elizabeth Morris-Baker wrote:
> >
>
> You need to send the TUR first, but yes,
> START_STOP will guarantee that you are
> ready to rock and roll.
> The first fix I wrote did a TUR, then
> 3 tries at a START_STOP, till it worked.
>
> cheers,
>
> Elizabeth
>
[deleted]
--
Torben Mathiasen <tmm@kernel.dk>
Linux ThunderLAN maintainer
http://tlan.kernel.dk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-02 23:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 21:49 scsi init problem in 2.4.0-test10? chen, xiangping
2000-11-02 21:58 ` Elizabeth Morris-Baker
2000-11-02 22:53 ` Matthew Dharm
2000-11-02 22:45 ` Elizabeth Morris-Baker
2000-11-02 23:50 ` Torben Mathiasen [this message]
2000-11-03 0:24 ` scsi init problem in 2.4.0-test10? [PATCH] Elizabeth Morris-Baker
2000-11-03 1:02 ` David Weinehall
2000-11-03 1:44 ` Elizabeth Morris-Baker
2000-11-03 1:37 ` scsi init problem in 2.4.0-test10? stefan mojschewitsch
-- strict thread matches above, loose matches on Subject: below --
2000-11-02 23:24 chen, xiangping
2000-11-03 0:49 chen, xiangping
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=20001103005034.C1353@torben \
--to=torben@kernel.dk \
--cc=chen_xiangping@emc.com \
--cc=eamb@liu.fafner.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdharm-kernel@one-eyed-alien.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.