see any reason not to move that resource into the northbridge
to avoid that issue. It's a simple fix. Is there a good reason for
having the MMCONF BAR in the APIC cluster?
This is what I was thinking. Build
Signed-off-by: Myles Watson <mylesgw(a)gmail.com>
Thanks Myles. I tested using the Kino project. With mmconf_base_address
set to e0000000, mmconf_bus_number set to 256, and no patch, booting
hangs in vbios init. Adding the patch allows it to boot, and I find no
bars overlapping the mmconf area. This patch seems to solve the problem
for me. If I get a chance, I will try Win7 boot also.
I'm glad it worked. The next thing would be to fix it so that it didn't
have to be in a fixed location. It should be relatively easy to do.