From: David Monro <davidm@amberdata.demon.co.uk>
To: Linux/ppc Dev List <linuxppc-dev@lists.linuxppc.org>
Subject: Prep interrupt routing (carolina-type board)
Date: Wed, 12 Apr 2000 01:54:18 +0100 [thread overview]
Message-ID: <38F3C93A.5BEDC95F@amberdata.demon.co.uk> (raw)
Hi all,
Does anybody know for sure if the ibm8xx_pci_IRQ_map structure in
prep_pci.c is correct? I'm trying to use an ncr53c825 board in one of
the PCI slots, and I'm getting the exact symptoms I used to get on my
intel box when the PCI bios screwed up and assigned the wrong irq to it
(it goes into an endless loop:
scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0,
lun 0 Te
st Unit Ready 00 00 00 00 00
ncr53c8xx_abort: pid=0 serial_number=1 serial_number_at_timeout=1
etc...)
Should the PCI interrupts turn up in the residual data in one of these
boards?
Cheers,
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-04-12 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-12 0:54 David Monro [this message]
2000-04-12 7:45 ` Prep interrupt routing (carolina-type board) Gabriel Paubert
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=38F3C93A.5BEDC95F@amberdata.demon.co.uk \
--to=davidm@amberdata.demon.co.uk \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).