From: Kumar Gala <galak@kernel.crashing.org>
To: Carlos Mitidieri <carlos.mitidieri@sysgo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: pci-x
Date: Fri, 24 Mar 2006 08:53:57 -0600 [thread overview]
Message-ID: <24661B8C-C4DF-4D9C-8F4A-F2E6600AFFE2@kernel.crashing.org> (raw)
In-Reply-To: <200603241221.44576.carlos.mitidieri@sysgo.com>
On Mar 24, 2006, at 5:21 AM, Carlos Mitidieri wrote:
>
> On Thursday 23 March 2006 16:41, Kumar Gala wrote:
>>> Is there PCI-X support for the mpc8540ads?
>>
>> Yes. You have to make sure the board is setup (switches in the right
>> place) properly for it.
>
> Thank you for answering.
>
> Looking the manuals and schematics, I have changed the "config"
> switch in
> SW1, and now the PCI-X support is activated in the kernel at the
> system
> initialization. Nevertheless, when I plug a bridge board to the
> slot 0, I
> get the following messages:
>
> PCI: Probing PCI hardware
> PCI: Cannot allocate resource region 1 of PCI bridge 1
> PCI: bridge 1 resource 1 moved to 9ff00000..9fffffff
> PCI: Cannot allocate resource region 2 of PCI bridge 1
> PCI: bridge 1 resource 2 moved to 9fe00000..9fefffff
>
> Would you guess that this is a driver problem, or that my board
> setup is still
> incorrect?
That seems like a driver problem. Does lspci show your devices after
you boot? Also, what kernel ver are you using?
- k
next prev parent reply other threads:[~2006-03-24 14:54 UTC|newest]
Thread overview: 9+ 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 ` Kumar Gala [this message]
2006-03-24 15:07 ` pci-x Carlos Mitidieri
2006-03-28 14:51 ` pci-x Carlos Mitidieri
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
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=24661B8C-C4DF-4D9C-8F4A-F2E6600AFFE2@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=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 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).