All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Matthew Wilcox <willy@debian.org>
Cc: Andrew Morton <akpm@osdl.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: sym2 probs in bk-scsi tree
Date: 08 Apr 2004 11:59:19 -0500	[thread overview]
Message-ID: <1081443560.2165.329.camel@mulgrave> (raw)
In-Reply-To: <20040408145700.GB18329@parcelfarce.linux.theplanet.co.uk>

On Thu, 2004-04-08 at 09:57, Matthew Wilcox wrote:
> They certainly are scary.  What is device 15 on this scsi bus?  This
> looks like domain validation being applied to a device that can't do it
> to me.  Did I get that right, James?

OK, try the attached, it should predicate DV on what we already know
from the inquiry data.

James

===== drivers/scsi/scsi_transport_spi.c 1.9 vs edited =====
--- 1.9/drivers/scsi/scsi_transport_spi.c	Thu Apr  8 08:39:09 2004
+++ edited/drivers/scsi/scsi_transport_spi.c	Thu Apr  8 12:35:07 2004
@@ -490,7 +490,7 @@
 	}
 
 	/* test width */
-	if (i->f->set_width) {
+	if (i->f->set_width && sdev->wdtr) {
 		i->f->set_width(sdev, 1);
 
 		if (!spi_dv_device_compare_inquiry(sreq, buffer,
@@ -502,6 +502,10 @@
 	}
 
 	if (!i->f->set_period)
+		return;
+
+	/* device can't handle synchronous */
+	if(!sdev->ppr && !sdev->sdtr)
 		return;
 
 	/* now set up to the maximum */


  parent reply	other threads:[~2004-04-08 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08  6:18 sym2 probs in bk-scsi tree Andrew Morton
2004-04-08 14:57 ` Matthew Wilcox
2004-04-08 15:16   ` Brian King
2004-04-08 15:40     ` Matthew Wilcox
2004-04-08 15:51       ` Brian King
2004-04-08 16:03   ` James Bottomley
2004-04-08 16:59   ` James Bottomley [this message]
2004-04-08 20:35     ` Andrew Morton

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=1081443560.2165.329.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=linux-scsi@vger.kernel.org \
    --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 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.