From: Kumar Gala <galak@kernel.crashing.org>
To: Clint Thomas <cthomas@Soneticom.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: PCI resource allocation MPC8540ADS
Date: Wed, 23 Aug 2006 18:06:26 -0500 [thread overview]
Message-ID: <09339AC2-6F79-4261-92B8-3068A4B33876@kernel.crashing.org> (raw)
In-Reply-To: <3C02138692C13C4BB675FE7EA240952918DFB7@bluefin.Soneticom.local>
On Aug 23, 2006, at 4:11 PM, Clint Thomas wrote:
> Hey guys,
>
> I have a development board based loosely off the MPC8540ADS design
> that I am trying to move to the Linux kernel 2.6. I already have
> this system working successfully in Linux Kernel 2.4, but after
> dealing with compilation and load errors, i've come to the point
> where I can get to a console. However, this problem at boot time
> keeps me from using a lot of onboard hardware. When I enable PCI
> support in the Kernel configuration, this is the text I get at boot
> time...
which 2.6 kernel are you using?
> PCI: Probing PCI hardware
> PCI: Cannot allocate resource region 1 of PCI bridge 1
> PCI: Cannot allocate resource region 2 of PCI bridge 1
> PCI: bridge 1 resource 2 moved to 9ff00000..9fffffff
> PCI: Cannot allocate resource region 1 of PCI bridge 2
> PCI: Cannot allocate resource region 2 of PCI bridge 2
> PCI: bridge 2 resource 2 moved to 9fe00000..9fefffff
> PCI: Cannot allocate resource region 1 of device 0000:00:14.0
> PCI: Cannot allocate resource region 2 of device 0000:00:14.0
> PCI: Cannot allocate resource region 0 of device 0000:01:01.0
> PCI: Cannot allocate resource region 1 of device 0000:01:01.0
> PCI: Cannot allocate resource region 2 of device 0000:01:01.0
> PCI: Cannot allocate resource region 0 of device 0000:01:05.0
> PCI: Cannot allocate resource region 1 of device 0000:01:05.0
> PCI: Cannot allocate resource region 2 of device 0000:01:05.0
> PCI: Cannot allocate resource region 0 of device 0000:01:06.0
> PCI: Cannot allocate resource region 0 of device 0000:01:06.1
> PCI: Cannot allocate resource region 0 of device 0000:01:06.2
> PCI: Failed to allocate mem resource #0:1000000@0 for 0000:01:01.0
> PCI: Failed to allocate I/O resource #1:100@1000 for 0000:01:01.0
> PCI: Failed to allocate mem resource #2:1000@0 for 0000:01:01.0
> PCI: Failed to allocate mem resource #0:10000@0 for 0000:01:05.0
> PCI: Failed to allocate mem resource #2:10000@0 for 0000:01:05.0
> PCI: Failed to allocate mem resource #0:1000@0 for 0000:01:06.0
> PCI: Failed to allocate mem resource #0:1000@0 for 0000:01:06.1
> PCI: Failed to allocate mem resource #0:100@0 for 0000:01:06.2
>
> the system is using a PLX PCI bridge chip. Like I said, this works
> fine in my 2.4 distribution. Thanks for any and all help!
can you post an lspci -v output.
- kumar
prev parent reply other threads:[~2006-08-23 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 21:11 PCI resource allocation MPC8540ADS Clint Thomas
2006-08-23 23:06 ` Kumar Gala [this message]
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=09339AC2-6F79-4261-92B8-3068A4B33876@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=cthomas@Soneticom.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