From: Doug Ledford <dledford@redhat.com>
To: Matthew Wilcox <willy@debian.org>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-scsi mailing list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] sym53c8xx PPR negotiation fix
Date: Wed, 29 Oct 2003 13:02:28 -0500 [thread overview]
Message-ID: <1067450547.3112.363.camel@compaq.xsintricity.com> (raw)
In-Reply-To: <20031029175045.GC25237@parcelfarce.linux.theplanet.co.uk>
On Wed, 2003-10-29 at 12:50, Matthew Wilcox wrote:
> On Wed, Oct 29, 2003 at 11:11:28AM -0600, James Bottomley wrote:
> > On Wed, 2003-10-29 at 11:07, Doug Ledford wrote:
> > > I haven't checked if this is applicable to 2.6 as well. James?
> >
> > Well, the sym driver doesn't exist anymore in 2.6...however sym_2 had a
> > similar issue. Matthew Wilcox has already fixed it though, I think.
>
> Oh, wishful thinking. I'm trying to fix it and haven't succeeded yet.
> These days, there's a PPR bit in the scsi_device, but it never seems to
> be set, so we don't even try negotiating it. Maybe the drives I have
> to play with aren't really U160.
>
> my current patch looks something like this (terribly mangled):
>
> @@ -518,16 +518,21 @@ static int sym_queue_command(struct sym_
> order = (lp && lp->s.reqtags) ? M_SIMPLE_TAG : 0;
>
> + /* Ensure we don't issue unwanted negotiations */
> + if (!ccb->device->ppr) {
> + tp->tinfo.goal.options &= ~PPR_OPT_MASK;
> + }
> +
Well, I do believe I recall adding the ppr bit to the scsi_device struct
long ago, and I thought I added the test to set it. If not, then on
device scan once we have the inquiry return data and have determined
scsi level of the device this would be sufficient to properly set it:
if (sdev->scsi_level >= 3 || (inquiry_len >= 53 && inquiry[56] & 0x04))
sdev->ppr = 1;
(I mainly added this so that drivers could rip out their INQUIRY
snooping code and rely upon the mid layer's snooping of INQUIRY to set
the relevant options, but I'm not sure that it's been completed well
enough that the drivers can do that yet)
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
next prev parent reply other threads:[~2003-10-29 18:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 17:07 [PATCH] sym53c8xx PPR negotiation fix Doug Ledford
2003-10-29 17:11 ` James Bottomley
2003-10-29 17:50 ` Matthew Wilcox
2003-10-29 18:02 ` Doug Ledford [this message]
[not found] ` <20031029183159.GE25237@parcelfarce.linux.theplanet.co.uk>
2003-10-29 18:45 ` Doug Ledford
2003-10-31 23:55 ` Justin T. Gibbs
2003-10-31 23:55 ` James Bottomley
2003-11-01 0:08 ` Doug Ledford
2003-11-01 0:16 ` Justin T. Gibbs
2003-11-01 1:22 ` Mike Anderson
2003-11-01 2:34 ` James Bottomley
2003-11-01 3:09 ` Doug Ledford
2003-11-03 18:10 ` Mike Anderson
2003-11-04 7:10 ` Christoph Hellwig
2003-11-05 9:26 ` Mike Anderson
2003-11-06 9:04 ` Mike Anderson
2003-11-06 9:07 ` Christoph Hellwig
2003-11-06 9:21 ` Mike Anderson
2003-11-01 0:02 ` Doug Ledford
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=1067450547.3112.363.camel@compaq.xsintricity.com \
--to=dledford@redhat.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=willy@debian.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