> firstname.lastname@example.org said:
> > However, it's entirely possible that you will be allocated resource
> > ranges that are intermingled with the ranges that are behind other
> > bridges or devices. There's no sane way to program the hotplug
> > bridge's BARs in such a situation.
> Why? Can't you just forward transactions for the whole of the range,
> including some addresses which are actually behind other bridges?
My copy of "PCI System Architecture, 4th Edition", say on the top of
On power-up, the system must be automatically configured so that each
device's IO and memory functions occupy mutually-exclusive address
There's no detail on what happens if you violate this, however. Digging
out the "PCI Local Bus Specification, Revision 2.2", section 3.2.2 (page
When a transaction is initiated on the interface, each potential target
compares the address with its Base Address register(s) to determine if
it is the target of the current transaction. If it is the target, the
device asserts DEVSEL# to claim the access. For more details about
DEVSEL# generation, refer to Section 3.6.1.
May take on that, as well as a quick read of section 3.6.1, is that
multiple targets claiming an address results in undefined behaviour,
since no mechanisms for handling that are defined in the spec.
-- Scott Murray SOMA Networks, Inc. Toronto, Ontario e-mail: email@example.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/