From: Linus Torvalds <torvalds@osdl.org>
To: Andreas Koch <koch@esa.informatik.tu-darmstadt.de>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
gregkh@suse.de
Subject: Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
Date: Fri, 3 Jun 2005 17:22:57 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0506031706450.1876@ppc970.osdl.org> (raw)
In-Reply-To: <20050603232828.GA29860@erebor.esa.informatik.tu-darmstadt.de>
On Sat, 4 Jun 2005, Andreas Koch wrote:
>
> While all of the USB and FireWire devices are visible using config
> space reads, they cannot be accessed correctly (all normal reads
> appear to return 0xff). After checking the dmesg logs, I find
>
> PCI: Cannot allocate resource region 7 of bridge 0000:02:00.0
> PCI: Cannot allocate resource region 8 of bridge 0000:02:00.0
Well, that would be right, because the parent of that bridge doesn't seem
to have any resources set up:
0000:00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 04) (prog-if 00 [Normal decode])
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 08
Bus: primary=00, secondary=02, subordinate=04, sec-latency=0
I/O behind bridge: 00000000-00000fff
Memory behind bridge: 00000000-000fffff
Prefetchable memory behind bridge: 0000000000000000-0000000000000000
the "IO/memory behind bridge" things don't seem to be making a lot of
sense.
Hmm. Normally on PC's we let the BIOS worry about PCI bridge resource
setup. The hotplug code knows about the setup-bus stuff too, but the
_normal_ PCI bus resouces are usually left alone. It looks like maybe we
shouldn't do that any more for PCI Express.
Hmm.. Just a wild guess (and this may not work at _all_, so who knows..):
how about adding a
pci_assign_unassigned_resources();
call to the end of "pcibios_init()" in arch/i386/pci/common.c ?
NOTE! In order for that to even link, you need to make sure that you have
CONFIG_HOTPLUG enabled, otherwise x86 won't have even linked in the bus
resource code from drivers/pci/setup-bus.c. And even so, I won't guarantee
that it does anything sane...
(I'm really surprised that we've gone this long without havign x86 do the
bus setup, though. So I'd not be in the least surprised if we need
_something_ like this, I'm just not at all sure that just adding that
single line won't do something disastrously bad..)
Linus
next prev parent reply other threads:[~2005-06-04 0:21 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 23:28 PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped Andreas Koch
2005-06-04 0:22 ` Linus Torvalds [this message]
2005-06-04 1:33 ` Andreas Koch
2005-06-04 1:55 ` Linus Torvalds
2005-06-04 2:26 ` Andreas Koch
2005-06-04 4:50 ` Linus Torvalds
2005-06-04 15:57 ` Andreas Koch
2005-06-05 16:46 ` Ivan Kokshaysky
2005-06-06 0:27 ` Andreas Koch
2005-06-06 14:43 ` Ivan Kokshaysky
2005-06-08 17:34 ` Andreas Koch
2005-06-08 22:36 ` Ivan Kokshaysky
2005-06-09 0:29 ` Andreas Koch
2005-06-09 4:04 ` Benjamin Herrenschmidt
2005-06-09 13:54 ` Ivan Kokshaysky
2005-06-09 17:54 ` Andreas Koch
2005-06-09 22:38 ` Andreas Koch
2005-06-09 23:20 ` Linus Torvalds
2005-06-10 14:33 ` Andreas Koch
2005-06-10 14:48 ` Ivan Kokshaysky
2005-06-10 20:47 ` Andreas Koch
2005-06-10 23:50 ` Sean Bruno
2005-06-14 15:19 ` Sean Bruno
2005-06-16 14:20 ` Andreas Koch
2005-06-16 17:20 ` Peter Buckingham
2005-06-16 20:53 ` Sean Bruno
2005-06-16 21:05 ` Peter Buckingham
2005-06-16 21:12 ` Roland Dreier
2005-06-16 21:21 ` Peter Buckingham
2005-06-17 9:54 ` Ivan Kokshaysky
2005-06-17 16:34 ` Peter Buckingham
2005-06-17 16:51 ` Sean Bruno
2005-06-17 17:59 ` Sean Bruno
2005-06-18 7:45 ` Ivan Kokshaysky
2005-06-18 17:55 ` Sean Bruno
2005-06-20 16:51 ` Peter Buckingham
2005-06-20 21:31 ` Peter Buckingham
2005-06-20 23:39 ` Peter Buckingham
2005-06-04 15:17 ` Linus Torvalds
2005-06-04 6:38 ` Greg KH
2005-06-04 6:51 ` Grant Grundler
2005-06-04 7:12 ` Grant Grundler
2005-06-04 7:19 ` Greg KH
2005-06-04 6:46 ` Greg KH
2005-06-04 16:16 ` Andreas Koch
2005-06-11 5:33 linux
2005-06-11 10:26 ` Ivan Kokshaysky
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=Pine.LNX.4.58.0506031706450.1876@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=gregkh@suse.de \
--cc=koch@esa.informatik.tu-darmstadt.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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).