All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Mitidieri <carlos.mitidieri@sysgo.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: pci-x
Date: Tue, 28 Mar 2006 16:51:52 +0200	[thread overview]
Message-ID: <200603281651.53196.carlos.mitidieri@sysgo.com> (raw)
In-Reply-To: <200603241607.35267.carlos.mitidieri@sysgo.com>


> On Friday 24 March 2006 15:53, Kumar Gala wrote:
> > That seems like a driver problem.  Does lspci show your devices after
> > you boot?  Also, what kernel ver are you using?
>
> No, the device behind the bridge is not recognized, although the bridge
> itself is. I am using kernel 2.6.15.

I am trying to use a PCI-X bridge (Intel 31154) on a mpc8540ads running kernel 
2.6.15.  A USB controller is behind the bridge. 

When the mpc8540ads is booted with the PCI-X switch disabled, the device 
behind the bridge is detected (and actually works), and the following 
messages are printed:

PCI: bridge rsrc 0..ffffff (100), parent c01ce78c
PCI: bridge rsrc 80000000..9fffffff (200), parent c01ce770
PCI: bridge rsrc fff000..ffffff (101), parent c0217038
PCI: bridge rsrc 9ff00000..9fffffff (200), parent c0217054
PCI: bridge rsrc 9fe00000..9fefffff (1201), parent c0217054
PCI:0000:01:06.0: Resource 0: 9ffff000-9fffffff (f=200)
PCI:0000:01:06.0: Resource 1: 9ffe0000-9ffeffff (f=1208)
PCI:0000:01:06.0: Resource 2: 9ffd0000-9ffdffff (f=200)
 
The last three lines are for the usb controller.
On the other hand, if the PCI-X is enabled, the usb controller is not detected 
anymore and the messages become:

PCI: bridge rsrc 0..ffffff (100), parent c01ce78c
PCI: bridge rsrc 80000000..9fffffff (200), parent c01ce770
PCI: bridge rsrc 0..fff (101), parent c0217038
PCI: bridge rsrc 0..fffff (200), parent c0217054
PCI: Cannot allocate resource region 1 of PCI bridge 1
PCI: bridge 1 resource 1 moved to 9ff00000..9fffffff
PCI: bridge rsrc 0..fffff (1201), parent c0217054
PCI: Cannot allocate resource region 2 of PCI bridge 1
PCI: bridge 1 resource 2 moved to 9fe00000..9fefffff

In the 3rd and 4th lines, the resource addresses are different for the two 
runs.  What could be the reason?

-- 
Carlos Mitidieri
SYSGO AG - Office Ulm

  reply	other threads:[~2006-03-28 14:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23 13:35 pci-x Carlos Mitidieri
2006-03-23 15:41 ` pci-x Kumar Gala
2006-03-24 11:21   ` pci-x Carlos Mitidieri
2006-03-24 14:53     ` pci-x Kumar Gala
2006-03-24 15:07       ` pci-x Carlos Mitidieri
2006-03-28 14:51         ` Carlos Mitidieri [this message]
2006-03-30 16:28           ` pci-x Andy Fleming
2006-03-31  6:52             ` pci-x Carlos Mitidieri
2006-03-31 11:50               ` pci-x Vitaly Bordug
  -- strict thread matches above, loose matches on Subject: below --
2001-05-26  7:04 PCI-X sanjay kumar

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=200603281651.53196.carlos.mitidieri@sysgo.com \
    --to=carlos.mitidieri@sysgo.com \
    --cc=linuxppc-embedded@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.