From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Cc: kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: Bamboo PCI interrupt issues
Date: Tue, 4 Mar 2008 07:15:21 +0100 [thread overview]
Message-ID: <200803040715.22301.sr@denx.de> (raw)
In-Reply-To: <20080303213718.12291eee@zod.rchland.ibm.com>
On Tuesday 04 March 2008, Josh Boyer wrote:
> > Is anybody using Bamboo PCI support right now? Does it actually work?
>
> I plugged in an old 3Com ethernet card tonight. Slot 0. It was
> assigned dev #4 IRQ 25. Using the device tree as-is, I could see
> interrupts happening in /proc/interrupts but ethernet traffic failed.
>
> Then I changed the sense level to 4 as you suggested, and my card hung
> hard on the first ethernet traffic.
Using '8' is correct. PCI interrupts are *always* level sensitive and active
low.
> I've no idea if we're dealing with
> a crappy card or a crappy driver but the device tree seems to be
> working ok. If I can find a different card to test with I will.
One thing always worth to check on 4xx IRQ problems is, if the external IRQ
pins are configured correctly for IRQ usage. Most of the times, the external
IRQ's are shared with other peripheral pins and/or GPIO pins. This
configuration is done in the GPIO core (and sometimes SDR PFCx registers).
This should be done correctly by the bootloader but sometimes the
configuration is wrong. I have to admit that I probably never tested PCI on
Bamboo. Just a thought.
Best regards,
Stefan
next prev parent reply other threads:[~2008-03-04 6:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 0:02 Bamboo PCI interrupt issues Hollis Blanchard
2008-03-04 0:59 ` David Gibson
2008-03-04 1:42 ` Benjamin Herrenschmidt
2008-03-04 1:53 ` David Gibson
2008-03-04 2:07 ` Segher Boessenkool
2008-03-04 2:15 ` David Gibson
2008-03-04 3:37 ` Josh Boyer
2008-03-04 6:15 ` Stefan Roese [this message]
2008-03-04 6:33 ` Benjamin Herrenschmidt
2008-03-04 20:39 ` Segher Boessenkool
2008-03-04 20:41 ` Benjamin Herrenschmidt
2008-03-04 20:59 ` Segher Boessenkool
2008-03-04 21:01 ` Benjamin Herrenschmidt
2008-03-04 6:18 ` Benjamin Herrenschmidt
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=200803040715.22301.sr@denx.de \
--to=sr@denx.de \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.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).