From: James Bottomley <James.Bottomley@SteelEye.com>
To: Tony Vroon <chainsaw@gentoo.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: aic7xxx regression occuring after 2.6.12 final
Date: Sat, 02 Jul 2005 14:46:14 -0500 [thread overview]
Message-ID: <1120333574.5073.26.camel@mulgrave> (raw)
In-Reply-To: <1120331026.22021.2.camel@localhost>
On Sat, 2005-07-02 at 20:03 +0100, Tony Vroon wrote:
> As you predicted, it tried but gave up.
Well, I've looked more closely at this. There's no support in either
the core or the sequencer for IU or QAS, so I think the safe course is
just to strip them out of the transport parameters (I don't have the
sequencer docs anyway, so there's no way I can correct the problem).
This should, therefore, get the whole lot booting again.
James
diff --git a/drivers/scsi/aic7xxx/aic7xxx_osm.c b/drivers/scsi/aic7xxx/aic7xxx_osm.c
--- a/drivers/scsi/aic7xxx/aic7xxx_osm.c
+++ b/drivers/scsi/aic7xxx/aic7xxx_osm.c
@@ -2633,6 +2633,11 @@ static void ahc_linux_set_dt(struct scsi
ahc_unlock(ahc, &flags);
}
+#if 0
+/* FIXME: This code claims to support IU and QAS. However, the actual
+ * sequencer code and aic7xxx_core have no support for these parameters and
+ * will get into a bad state if they're negotiated. Do not enable this
+ * unless you know what you're doing */
static void ahc_linux_set_qas(struct scsi_target *starget, int qas)
{
struct Scsi_Host *shost = dev_to_shost(starget->dev.parent);
@@ -2688,6 +2693,7 @@ static void ahc_linux_set_iu(struct scsi
ppr_options, AHC_TRANS_GOAL, FALSE);
ahc_unlock(ahc, &flags);
}
+#endif
static struct spi_function_template ahc_linux_transport_functions = {
.set_offset = ahc_linux_set_offset,
@@ -2698,10 +2704,12 @@ static struct spi_function_template ahc_
.show_width = 1,
.set_dt = ahc_linux_set_dt,
.show_dt = 1,
+#if 0
.set_iu = ahc_linux_set_iu,
.show_iu = 1,
.set_qas = ahc_linux_set_qas,
.show_qas = 1,
+#endif
};
next prev parent reply other threads:[~2005-07-02 19:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 22:50 aic7xxx regression occuring after 2.6.12 final Tony Vroon
2005-07-02 15:42 ` Tony Vroon
2005-07-02 16:22 ` James Bottomley
2005-07-02 16:46 ` Tony Vroon
2005-07-02 17:01 ` James Bottomley
2005-07-02 17:13 ` Tony Vroon
2005-07-02 17:33 ` James Bottomley
2005-07-02 17:47 ` Tony Vroon
2005-07-02 18:36 ` James Bottomley
2005-07-02 19:03 ` Tony Vroon
2005-07-02 19:15 ` Tony Vroon
2005-07-02 19:46 ` James Bottomley [this message]
2005-07-02 20:04 ` Tony Vroon
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=1120333574.5073.26.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=apw@shadowen.org \
--cc=chainsaw@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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