From: Olaf Hering <olaf@aepfle.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.18-rc6
Date: Thu, 7 Sep 2006 11:15:17 +0200 [thread overview]
Message-ID: <20060907091517.GA21728@aepfle.de> (raw)
In-Reply-To: <1157551480.3469.8.camel@mulgrave.il.steeleye.com>
On Wed, Sep 06, James Bottomley wrote:
> On Wed, 2006-09-06 at 13:01 +0200, Olaf Hering wrote:
> > This causes another machine check because it runs ahc_inb(ahc, SBLKCTL) again.
> > With debug I get:
>
> Exactly. It's not a card state problem; the register simply doesn't
> exist. It looks like from the source code, it only exists on twin or U2
> and above chipsets (i.e. those supporting LVD).
>
> Try this patch, which should deduce the bus type for U and below without
> resorting to the SBLKCTL register.
>
> James
>
> diff --git a/drivers/scsi/aic7xxx/aic7xxx_osm.c b/drivers/scsi/aic7xxx/aic7xxx_osm.c
> index e5bb4d8..0b3c01a 100644
> --- a/drivers/scsi/aic7xxx/aic7xxx_osm.c
> +++ b/drivers/scsi/aic7xxx/aic7xxx_osm.c
> @@ -2539,15 +2539,23 @@ #endif
> static void ahc_linux_get_signalling(struct Scsi_Host *shost)
> {
> struct ahc_softc *ahc = *(struct ahc_softc **)shost->hostdata;
> - u8 mode = ahc_inb(ahc, SBLKCTL);
> + u8 mode;
>
> - if (mode & ENAB40)
> - spi_signalling(shost) = SPI_SIGNAL_LVD;
> - else if (mode & ENAB20)
> + if (!(ahc->features & AHC_ULTRA2)) {
This does not work: ahc_linux_get_signalling: f 56f6
echo $(( 0x56f6 & 0x00002 )) gives 2, and the ahc_inb is called.
next prev parent reply other threads:[~2006-09-07 9:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 2:42 Linux 2.6.18-rc6 Linus Torvalds
2006-09-04 11:05 ` Gene Heskett
2006-09-04 22:31 ` Steffen Klassert
2006-09-05 0:17 ` Gene Heskett
2006-09-05 16:04 ` Alistair John Strachan
2006-09-05 20:02 ` Gene Heskett
2006-09-22 9:10 ` Konstantin Kletschke
2006-09-05 12:26 ` Olaf Hering
2006-09-05 12:45 ` maximilian attems
2006-09-05 18:56 ` Greg KH
2006-09-05 19:01 ` maximilian attems
2006-09-05 21:50 ` Greg KH
2006-09-05 21:01 ` James Bottomley
2006-09-05 22:20 ` Benjamin Herrenschmidt
2006-09-05 23:22 ` James Bottomley
2006-09-06 0:47 ` Benjamin Herrenschmidt
2006-09-06 12:09 ` Olaf Hering
2006-09-06 11:01 ` Olaf Hering
2006-09-06 14:04 ` James Bottomley
2006-09-07 9:15 ` Olaf Hering [this message]
2006-09-07 14:04 ` James Bottomley
2006-09-16 3:47 ` Doug Ledford
2006-09-16 8:44 ` Olaf Hering
2006-09-17 5:38 ` Olaf Hering
2006-09-17 14:05 ` James Bottomley
2006-09-17 18:17 ` Doug Ledford
2006-09-17 18:20 ` Doug Ledford
-- strict thread matches above, loose matches on Subject: below --
2006-09-12 15:04 Jody Belka
2006-09-12 22:33 ` Greg KH
2006-09-12 23:11 ` Jody Belka
2006-09-13 0:42 ` Jody Belka
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=20060907091517.GA21728@aepfle.de \
--to=olaf@aepfle.de \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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