ron minnich wrote:
yes, and thinking about it ... there's only one bridge anywhere in the system that is going to decode legacy IO, or mem, or vsa (not always same bridge).
I wonder if it would be simpler to have a property to mark these bridges in the dts. It can not be determined -- code has to know that a given piece of hardware is decoding the legacy range.
It adds constraints to resource allocation so it has to be known. And it is property of hardware so it goes into the dts. :)
I think that makes sense!
//Peter