From: Matt Porter <porter@cox•net>
To: "William A. Gatliff" <bgat@billgatliff•com>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: PCI: Cannot allocate resource region {012}
Date: Wed, 12 Feb 2003 23:37:34 -0700 [thread overview]
Message-ID: <20030212233734.A32277@home.com> (raw)
In-Reply-To: <20030212222135.A7769@saturn.billgatliff.com>; from bgat@billgatliff.com on Wed, Feb 12, 2003 at 10:21:35PM -0600
On Wed, Feb 12, 2003 at 10:21:35PM -0600, William A. Gatliff wrote:
>
> Guys:
>
>
> I'm porting 2.4.20 to a custom MPC8245 system, based loosely on code
> from MV's 2.4.19, in particular the mpc10x.c.
>
> When my kernel boots, I see these:
>
> PCI: Cannot allocate resource region 0 of device 00:02.0
> PCI: Cannot allocate resource region 1 of device 00:02.0
> PCI: Cannot allocate resource region 2 of device 00:02.0
> ...
> PCI: Cannot allocate resource region 0 of device 00:1f.0
> PCI: Cannot allocate resource region 1 of device 00:1f.0
> PCI: Cannot allocate resource region 2 of device 00:1f.0
Bill,
Take a look at sandpoint_pci.c:sandpoint_exclude_device()
for an example of using the ppc_md.exclude_device. Have it
avoid bus 0 devfn 0 so it ignores your host bridge (doesn't
hit its IDSEL on the bus scan). That should cure your
system.
Regards,
--
Matt Porter
porter@cox•net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-02-13 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 4:21 PCI: Cannot allocate resource region {012} William A. Gatliff
2003-02-13 6:37 ` Matt Porter [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=20030212233734.A32277@home.com \
--to=porter@cox$(echo .)net \
--cc=bgat@billgatliff$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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