On Wed, 2008-03-26 at 13:14 +0300, Ivan Kokshaysky wrote:
quoted text
> 
> Yeah, it's resource issue for sure. The 00:1e.0 is a transparent
> bridge,
> so I blame commit 8fa5913d54f3b1e09948e6a0db34da887e05ff1f
> (PCI: remove transparent bridge sizing). It's wrong for two reasons:
> - we cannot ignore standard windows of a transparent bridge as they
>   always positive decode, so they are potential source of address
> conflicts;
> - that patch just broke whole bridge setup logic in unpredictable way.

The root of the problem is again HW vendors getting wild I think...

Some bridges are fully transparent, some have explicit decode windows
but are also transparent for whatever else and we definitely don't deal
with it.

Ben.


--
unsubscribe notice
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/