From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: linux@horizon.com
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
torvalds@osdl.org
Subject: Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
Date: Sat, 11 Jun 2005 14:26:58 +0400 [thread overview]
Message-ID: <20050611142658.A4952@jurassic.park.msu.ru> (raw)
In-Reply-To: <20050611053331.9203.qmail@science.horizon.com>; from linux@horizon.com on Sat, Jun 11, 2005 at 05:33:31AM -0000
On Sat, Jun 11, 2005 at 05:33:31AM -0000, linux@horizon.com wrote:
> Actually, that's not possible, because no difference is permitted.
Not possible on only on _real_ PCI bus.
Example: virtually every laptop has mobile bridge and ISA/LPC/whatever
bridge on the same bus segment. Both are subtractive decode devices -
impossible situation from classic PCI point of view. But it's just
happens because it's _not_ PCI but some proprietary bus, even if it looks
like PCI from software point of view. And sort of priority decode is
certainly takes place there.
Ivan.
next prev parent reply other threads:[~2005-06-11 10:27 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 5:33 PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped linux
2005-06-11 10:26 ` Ivan Kokshaysky [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-03 23:28 Andreas Koch
2005-06-04 0:22 ` Linus Torvalds
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
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=20050611142658.A4952@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux@horizon.com \
--cc=torvalds@osdl.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).