This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] RE: [SeaBIOS] [PATCH] Consider a VGA to be active if it resp

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>, <seabios@xxxxxxxxxxx>
Subject: [Xen-devel] RE: [SeaBIOS] [PATCH] Consider a VGA to be active if it responds to either IO or memory access
From: "Scott Duplichan" <scott@xxxxxxxxxx>
Date: Fri, 27 May 2011 11:02:35 -0500
Delivery-date: Fri, 03 Jun 2011 09:55:46 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=notabs.org; h=Received:From:To:References:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:In-Reply-To:X-MimeOLE:Thread-Index:X-Identified-User; b=GdnU8ZvdGIMmueqlnw8uPX1l5vl4cRh555tSB7eFd/HYnNqjJS3DesSeGIe/Ya+KXFR0RzoL0uvNm/P/6WCcWil3ChKrn8ANY+DEj1m3Mpx9elZ3nj9MP4+a6DT3j3+v;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1306485899.775.73.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1306421008-24260-1-git-send-email-ian.campbell@xxxxxxxxxx><20110527005919.GA31745@xxxxxxxxxxxxxxxx> <1306485899.775.73.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcwcSmvhqEVVDD5eRgebQIR3WcgK7QAOv/Ag
Ian Campbell wrote:

]It's not obvious whether the I/O space enable bit in the PCI cfg command
]register is supposed to control the availability of non-PCI registers or
]not. Neither the PCI spec nor the GD-5446 datasheet are particularly
]clear on the matter.

The VGA class code indicates that the legacy I/O ranges are decoded,
when enabled in the command register. True the PCI spec does not spell
this out. But there is really no other way it could work. The BAR 
mechanism does not provide a way to either report or accept programming
for a range such as 3b0-3bb.

]I've just discovered that the ancient pentium box I use as a home
]firewall has a GD 5446 in it (useful to know!), it doesn't have any I/O
]BARS but it does have the I/O bit set in the PCI command register.
]It's not clear who was responsible for setting that bit, in general in
]the absence of an I/O BAR the BIOS wouldn't know to do so. I expect that
]either the VGA BIOS is expected to enable it if the hardware it drives
]requires it or that BIOSen special case class=VGA devices and always
]enable I/O for one of them.

BIOS or some other firmware (coreboot) must enable I/O decode in 
the command register for VGA class devices. Option ROMs in general do
not enable it.

]It looks like coreboot always forces this bit on for the VGA device
]which it determines to be the primary, which is good enough for me --
]I'll make a patch to the Xen pci setup code to implement that instead of
]this change to SeaBIOS.

Yes, right here:


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] RE: [SeaBIOS] [PATCH] Consider a VGA to be active if it responds to either IO or memory access, Scott Duplichan <=