All of lore.kernel.org
 help / color / mirror / Atom feed
From: robinpv <robinpv@aiware.co.jp>
To: linuxppc-dev@ozlabs.org
Subject: MPC5200 PCI resource allocation problem
Date: Thu, 06 Jul 2006 16:17:02 +0900	[thread overview]
Message-ID: <44ACB8EE.6000406@aiware.co.jp> (raw)

Hi,
I am using the MPC5200 based board. I have a PCI 2250 bridge, with 2 
RTL8110S ethernet chips on the bridge.
I am using the lite5200 as reference code.
When i run the linux(2.6.16.1), during bootup the following messages are 
displayed,

PCI: Probing PCI hardware
PCI: Cannot allocate resource region 0 of PCI bridge 1
PCI: bridge 1 resource 0 moved to b0fff000..b0ffffff
PCI: Cannot allocate resource region 1 of PCI bridge 1
PCI: bridge 1 resource 1 moved to aff00000..afffffff
PCI: Cannot allocate resource region 2 of PCI bridge 1
PCI: bridge 1 resource 2 moved to 9ff00000..9fffffff

Looking at the iomem and ioports dump, shows that MMIO region has been 
allocated.
But in the ethernet driver when i try to access the ethernet registers. 
all the register content are shown as FFFF.
Also in the mpc52xx_pci.h, the default value for these macros are...
#define MPC52xx_PCI_IO_BASE       0xb0000000
#define MPC52xx_PCI_IO_START    0x00000000
For this setting, IO resource allocation fails
changing to
#define MPC52xx_PCI_IO_START    0xB0000000
passes through.

Can some suggest what could be the problem and how to go about.??

-------------------------------------------------------------------
the iomem dump is as follows
80000000-9fffffff : PCI prefetchable memory
  9ff00000-9fffffff : PCI Bus #01
a0000000-afffffff : PCI memory
  a0000000-a07fffff : 0000:00:10.0
  a0800000-a09fffff : 0000:00:10.0
    a0840000-a0840057 : ohci_hcd
  a0a00000-a0a000ff : 0000:00:11.0
    a0a00000-a0a000ff : SiI680
  a0a40000-a0a7ffff : 0000:00:1a.0
  aff00000-afffffff : PCI Bus #01
    aff00000-aff000ff : 0000:01:02.0
      aff00000-aff000ff : r8169 <= Ethernet 1
    aff00100-aff001ff : 0000:01:03.0
      aff00100-aff001ff : r8169 <=Ethernet 2
f0000900-f000097f : mpc52xx-mscan.0
f0000980-f00009ff : mpc52xx-mscan.1
f0000f00-f0000f1f : mpc52xx-spi
f0001000-f00010ff : ppc-soc-ohci
f0001300-f000130f : mpc52xx-bdlc
f0002000-f000209f : mpc52xx-psc.0
  f0002000-f000209f : mpc52xx_psc_uart
f0002200-f000229f : mpc52xx-psc.1
f0002400-f000249f : mpc52xx-psc.2
f0002600-f000269f : mpc52xx-psc.3
f0002800-f000289f : mpc52xx-psc.4
f0002c00-f0002c9f : mpc52xx-psc.5
f0003000-f00033ff : mpc52xx-fec
f0003a00-f0003aff : mpc52xx-ata
f0003d00-f0003d1f : fsl-i2c.0
f0003d40-f0003d5f : fsl-i2c.1
-------------------------------------------------------
the ioports dump is
  b0000000-b0000007 : 0000:00:11.0
  b0000008-b000000b : 0000:00:11.0
  b000000c-b000000f : 0000:00:11.0
  b0000010-b0000017 : 0000:00:11.0
  b0000020-b000002f : 0000:00:11.0
  b0fff000-b0ffffff : PCI Bus #01
    b0fff000-b0fff0ff : 0000:01:02.0
      b0fff000-b0fff0ff : r8169 <=Ethernet 1
    b0fff400-b0fff4ff : 0000:01:03.0
      b0fff400-b0fff4ff : r8169 <=Ethernet 2
----------------------------------------------------------

With Regards,
Robin

                 reply	other threads:[~2006-07-06  7:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=44ACB8EE.6000406@aiware.co.jp \
    --to=robinpv@aiware.co.jp \
    --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.