All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steven A. Falco" <sfalco@harris.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: [QUESTION] 440EPx with PCI to PCIe bridge error
Date: Mon, 05 Jan 2009 15:09:11 -0500	[thread overview]
Message-ID: <496268E7.5090907@harris.com> (raw)

I have a Sequoia board (440EPx) with kernel 2.6.27.9.  I've recently
plugged in a PLX adapter board to convert one of the PCI connectors
on the Sequoia to PCIe.

When the kernel boots, I get the following error messages regarding
mem resource allocation.  Device 0000:00:0c.0 is the PCI<->PCIe bridge,
and device 0000:01:00.0 is an FPGA PCIe evaluation board.

	PCI host bridge /plb/pci@1ec000000 (primary) ranges:
	 MEM 0x0000000180000000..0x000000018fffffff -> 0x0000000080000000
	  IO 0x00000001e8000000..0x00000001e80fffff -> 0x0000000000000000
	4xx PCI DMA offset set to 0x00000000
	PCI: Probing PCI hardware
	PCI: Hiding 4xx host bridge resources 0000:00:00.0
	pci 0000:00:0c.0: PME# supported from D0 D1 D3hot
	pci 0000:00:0c.0: PME# disabled
	pci 0000:00:0c.0: BAR 8: can't allocate mem resource [0x180000000-0x18fffffff]
	pci 0000:01:00.0: BAR 1: can't allocate mem resource [0x1f0000000-0x1ffffffff]
	pci 0000:01:00.0: BAR 0: can't allocate mem resource [0x180000000-0x18007ffff]
	pci 0000:00:0c.0: PCI bridge, secondary bus 0000:01
	pci 0000:00:0c.0:   IO window: disabled
	pci 0000:00:0c.0:   MEM window: disabled
	pci 0000:00:0c.0:   PREFETCH window: disabled

Plain PCI cards plugged directly into the Sequoia work fine.  Is there
something I have to add to the .dts file to represent the PCI<->PCIe
bridge?

	Thanks,
	Steve

             reply	other threads:[~2009-01-05 20:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 20:09 Steven A. Falco [this message]
2009-01-05 21:18 ` [QUESTION] 440EPx with PCI to PCIe bridge error Benjamin Herrenschmidt
2009-01-05 21:35   ` Steven A. Falco
2009-01-06  6:33     ` Benjamin Herrenschmidt
2009-01-06 14:44       ` Steven A. Falco
2009-01-06 18:33       ` Steven A. Falco
2009-01-06 20:41       ` Steven A. Falco
2009-01-06 21:38         ` Steven A. Falco
2009-01-06 22:02           ` Benjamin Herrenschmidt
2009-01-06 22:22             ` Steven A. Falco
2009-01-06 23:13               ` Benjamin Herrenschmidt
2009-01-07 14:45                 ` Steven A. Falco
2009-01-07 20:52                   ` 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=496268E7.5090907@harris.com \
    --to=sfalco@harris.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 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.