[coreboot] Patch set updated for coreboot: 6709bdd Fix multipleVGA cards resource conflict on Windows
tsylla at gmail.com
Tue Dec 20 04:33:35 CET 2011
The open-graphics people had this question a while back, I think I
took a look at some different platforms and BIOSes:
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 at amd.com> wrote:
> Hello, Patrick
>> -----Original Message-----
>> From: coreboot-bounces at coreboot.org
> [mailto:coreboot-bounces at coreboot.org]
>> On Behalf Of Patrick Georgi
>> Sent: Tuesday, December 20, 2011 1:31 AM
>> To: coreboot at 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,
>> > 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
>> other boot systems will support Windows even to the detriment of Linux
>> Which means that vgaarb wouldn't exist, given their position towards
> It make sense on the OS lacking a mechanism like vgaarb.
> Anyway, more test on different OS is needed.
>> > Changing circumstances mean I get to work on it
>> > again, which is nice.
>> coreboot mailing list: coreboot at coreboot.org
> coreboot mailing list: coreboot at coreboot.org
More information about the coreboot