linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: linuxppc-dev@ozlabs.org
Subject: PCI interrupt assignment on sequoia board
Date: Wed, 9 Jan 2008 16:53:22 +0100	[thread overview]
Message-ID: <200801091653.22478.matthias.fuchs@esd-electronics.com> (raw)

Hi,

I noticed that Josh's 'for-2.5.25' does not assign PCI interrupts correctly:

bash-3.00# lspci -v
00:00.0 Class 0680: 1014:027f
        Subsystem: 10e8:cafe
        Flags: bus master, medium devsel, latency 0, IRQ 16
        Memory at <unassigned> (32-bit, prefetchable)
        Capabilities: [58] Power Management version 2

00:0a.0 Class 0b20: 1014:027f	(this is a PPC440EPx PCI target board in a sequoia PCI slot)
        Subsystem: 12fe:0441
        Flags: bus master, medium devsel, latency 128, IRQ 16
        Memory at 0000000180000000 (32-bit, prefetchable) [size=64M]
        Memory at 0000000184000000 (32-bit, prefetchable) [size=16M]
        Capabilities: [58] Power Management version 2

00:0c.0 Class 0200: 168c:0013 (rev 01)
        Subsystem: 14b7:0a60
        Flags: bus master, medium devsel, latency 128, IRQ 16
        Memory at 0000000185000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [44] Power Management version 2

bash-3.00# uname -a
Linux sequoia 2.6.24-rc6-g78994e24 #5 Wed Jan 9 16:22:31 CET 2008 ppc ppc ppc GNU/Linux


All interrupts are '16'. But I expected 67 as correctly stated in the device tree.
This test has been made with the uboot wrapper code.

Any idea?

Matthias

             reply	other threads:[~2008-01-09 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 15:53 Matthias Fuchs [this message]
2008-01-09 16:04 ` PCI interrupt assignment on sequoia board Stefan Roese
2008-01-09 16:18 ` Josh Boyer

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=200801091653.22478.matthias.fuchs@esd-electronics.com \
    --to=matthias.fuchs@esd-electronics.com \
    --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).