> scottm@somanetworks.com said:
> > I think the implications are pretty strong that programming bridges
> > with conflicting ranges will result in undefined behaviour. Even if
> > it did work, doing so also has the potential to open us up to new
> > classes of bridge hardware bugs that no one has seen before.
>
> OK. That buggers that idea then :(
Do you have any objection to this boot time reservation stuff going in
for now as a cPCI only thing? I can imagine other solutions that use
DMI scans or the like to detect cPCI master cards and grab chunks of the
resource space(s) for the hotswap buses, but don't have any clever ideas
on reliable heuristics for knowing how big those chunks should be for a
given card.
Scott
-- Scott Murray SOMA Networks, Inc. Toronto, Ontario e-mail: scottm@somanetworks.com- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/