From: Matthew Wilcox <matthew@wil.cx>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Matthew Wilcox <willy@parisc-linux.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] [4/5] ncr53c8xx update
Date: Sun, 20 Mar 2005 01:32:28 +0000 [thread overview]
Message-ID: <20050320013228.GO21986@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1111278727.5525.33.camel@mulgrave>
On Sat, Mar 19, 2005 at 06:32:07PM -0600, James Bottomley wrote:
> On Fri, 2005-03-18 at 20:56 -0700, Matthew Wilcox wrote:
> > ncr53c8xx update
>
> There's actually a slight problem with this one: on my Q720 it produces
> messages like this:
>
> ncr53c720-1: ID 7, Fast-10, Parity Checking
> scsi1 : ncr53c8xx-3.4.3g
> target1:0:1: target did not report SYNC.
>
> Although everything is fine. The initial "target did not report SYNC"
> is because the driver is trying to negotiate over the initial inquiry
> (so, naturally we don't know if it supports sync yet). The solution is
> to rip out the last remnants of the spontaneous attempts at negotiation
> to force it to wait for the DV negotiation in slave_configure.
Wonderful, thanks for finding & fixing that.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
prev parent reply other threads:[~2005-03-20 1:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 3:56 [PATCH] [4/5] ncr53c8xx update Matthew Wilcox
2005-03-20 0:32 ` James Bottomley
2005-03-20 1:32 ` Matthew Wilcox [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=20050320013228.GO21986@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=willy@parisc-linux.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 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.