public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.5.59] sim710: cleanup/remove most cli()'s
Date: 11 Feb 2003 12:30:12 -0600	[thread overview]
Message-ID: <1044988215.1774.20.camel@mulgrave> (raw)
In-Reply-To: <200302111155.33075@bilbo.math.uni-mannheim.de>

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

On Tue, 2003-02-11 at 04:55, Rolf Eike Beer wrote:
> Am Samstag, 8. Februar 2003 04:57 schrieben Sie:
> > On Fri, 2003-02-07 at 01:26, Rolf Eike Beer wrote:
> > > That would be fine, you know your code better than I ever will.
> >
> > OK, the attached works for me for the 3430 MCA internal SCSI chip and an
> > HP EISA SCSI board.  Let me know how it works for the Compaq.
> 
> This is from my boot.msg:
> 
> <6>EISA bus registered
> <6>EISA: Probing bus...
> <6>EISA: Motherboard CPQ0601 detected
> <6>EISA: slot 2 : CPQ3011 detected.
> <6>EISA: slot 3 : CPQ6100 detected.
> <6>EISA: slot 7 : CPQ4411 detected.
> <6>EISA: slot 8 : CPQ4410 detected.
> <6>EISA: Detected 4 cards.
> 
> [...]
> 
> <5>IRQ_INDEX 249, 5
> <4>sim710: irq nasty
> 
> This is the Compaq NCR 53c710 on an EISA board, address 0x7000, IRQ 14 (and it 
> works fine with the original sim710).

Ah, OK, that's what I get for enabling something that was previously
disabled.  I suspected the disabled probe code had more than just the
IRQ coded into it.  It looks like only the three lower bits should be
used to determine the IRQ. I believe it will work if you apply this
patch.

James


[-- Attachment #2: tmp.diff --]
[-- Type: text/plain, Size: 368 bytes --]

===== drivers/scsi/sim710.c 1.8 vs edited =====
--- 1.8/drivers/scsi/sim710.c	Sun Feb  9 10:07:34 2003
+++ edited/drivers/scsi/sim710.c	Tue Feb 11 12:28:55 2003
@@ -307,7 +307,7 @@
 #endif
 	} else {
 		eisa_irqs = eisa_cpq_irqs;
-		irq_index = inb(io_addr + 0xc88);
+		irq_index = inb(io_addr + 0xc88) & 0x07;
 	}
 
 	if(irq_index >= strlen(eisa_irqs)) {

      reply	other threads:[~2003-02-11 18:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04 10:23 [PATCH 2.5.59] sim710: cleanup/remove most cli()'s Rolf Eike Beer
2003-02-04 11:34 ` Christoph Hellwig
2003-02-04 23:11 ` James Bottomley
2003-02-05 15:03 ` Rolf Eike Beer
2003-02-06 16:35   ` James Bottomley
2003-02-07  7:26   ` Rolf Eike Beer
2003-02-08  3:57     ` James Bottomley
2003-02-11 10:55       ` Rolf Eike Beer
2003-02-11 18:30         ` James Bottomley [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=1044988215.1774.20.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=eike-kernel@sf-tec.de \
    --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