From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Jeff Hane <jeff.hane@maxim-ic.com>
Subject: Re: PCI interrupt question
Date: Fri, 4 Dec 2009 05:52:34 +0100 [thread overview]
Message-ID: <200912040552.34178.sr@denx.de> (raw)
In-Reply-To: <1259869140.18190.52.camel@qu102.quarc.com>
On Thursday 03 December 2009 20:39:00 Jeff Hane wrote:
> > Can you clarify:
> >
> > 1. 460EX is your PCI host CPU?
>
> yes. We are using a canyonlands board with 460ex.
PCI works on Canyonlands without any problems. I just tested latest Linux
release (2.6.32) with an PCI USB card:
-bash-3.2# uname -a
Linux canyonlands 2.6.32 #1 Fri Dec 4 05:42:35 CET 2009 ppc ppc ppc GNU/Linux
-bash-3.2# cat /proc/cpuinfo
processor : 0
cpu : 460EX
clock : 800.000010MHz
revision : 24.162 (pvr 1302 18a2)
bogomips : 1600.00
timebase : 800000010
platform : PowerPC 44x Platform
model : amcc,canyonlands
Memory : 512 MB
-bash-3.2# cat /proc/interrupts
CPU0
18: 0 UIC Edge L2C
19: 22 UIC Level ohci_hcd:usb2, ohci_hcd:usb3
20: 15220 UIC Level serial
23: 8038 UIC Level MAL TX EOB
24: 15510 UIC Level MAL RX EOB
25: 0 UIC Level MAL SERR
26: 0 UIC Level MAL TX DE
27: 0 UIC Level MAL RX DE
28: 0 UIC Level EMAC
34: 1 UIC Level ohci_hcd:usb1
35: 2926 UIC Level IBM IIC
38: 0 UIC Level IBM IIC
BAD: 0
-bash-3.2#
I can't see any problems with PCI interrupts here.
Cheers,
Stefan
next prev parent reply other threads:[~2009-12-04 4:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 6:21 PCI interrupt question Jeff Hane
2009-12-03 7:31 ` Stefan Roese
2009-12-03 17:11 ` David Hawkins
2009-12-03 19:39 ` Jeff Hane
2009-12-03 19:44 ` Ira W. Snyder
2009-12-03 19:52 ` David Hawkins
2009-12-03 19:59 ` Ira W. Snyder
2009-12-03 20:03 ` David Hawkins
2009-12-03 21:28 ` Wolfgang Denk
2009-12-03 21:38 ` David Hawkins
2009-12-04 9:05 ` Benjamin Herrenschmidt
2009-12-04 4:52 ` Stefan Roese [this message]
2009-12-04 9:02 ` 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=200912040552.34178.sr@denx.de \
--to=sr@denx.de \
--cc=jeff.hane@maxim-ic.com \
--cc=linuxppc-dev@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.