The open-graphics people had this question a while back, I think I took a look at some different platforms and BIOSes: http://lists.duskglow.com/open-graphics/2007-August/010402.html
Turning on the decoders for only one of each type of legacy device sounds right.
On Mon, Dec 19, 2011 at 6:13 PM, She, Kerry Kerry.She@amd.com wrote:
Hello, Patrick
-----Original Message----- From: coreboot-bounces@coreboot.org
[mailto:coreboot-bounces@coreboot.org]
On Behalf Of Patrick Georgi Sent: Tuesday, December 20, 2011 1:31 AM To: coreboot@coreboot.org Subject: Re: [coreboot] Patch set updated for coreboot: 6709bdd Fix multipleVGA cards resource conflict on Windows
Am 19.12.2011 18:02, schrieb ron minnich:
I wonder if a better way to manage this is via a CMOS (aka NVRAM) setting.
No user visible configuration if it can be avoided, please.
I kind of hate to limit coreboot because Windows is limited. But I'm a n00b in a sense, having just come back onto this project,
so
I'm happy to be told I'm wrong :-)
It sounds just wrong to have IO/MEM decoding on the _same_ areas activated for two devices.
Yes, exactly.
vgaarb should still work with one of them having resources disabled by default, I think.
I have tested Linux vgaarb still works. We just do a part of the vgaarb job in coreboot.
Otherwise coreboot would be the _only_ chance for vgaarb to work, as
all
other boot systems will support Windows even to the detriment of Linux support. Which means that vgaarb wouldn't exist, given their position towards coreboot.
It make sense on the OS lacking a mechanism like vgaarb. Anyway, more test on different OS is needed. Thanks
Changing circumstances mean I get to work on it again, which is nice.
Yay!
Patrick
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot