From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IJuXy-0004vv-9A for qemu-devel@nongnu.org; Sat, 11 Aug 2007 13:14:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IJuXw-0004v6-JW for qemu-devel@nongnu.org; Sat, 11 Aug 2007 13:14:41 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IJuXw-0004v3-GW for qemu-devel@nongnu.org; Sat, 11 Aug 2007 13:14:40 -0400 Received: from nf-out-0910.google.com ([64.233.182.190]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IJuXw-0000YX-4f for qemu-devel@nongnu.org; Sat, 11 Aug 2007 13:14:40 -0400 Received: by nf-out-0910.google.com with SMTP id 30so364661nfu for ; Sat, 11 Aug 2007 10:14:39 -0700 (PDT) Message-ID: Date: Sat, 11 Aug 2007 19:14:39 +0200 From: "andrzej zaborowski" Subject: Re: [Qemu-devel] [PATCH/RFC] Set a (distinguishable) subsystem id for Cirrus VGA In-Reply-To: <46BCB48A.9050408@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1186687670.26986.19.camel@erebor.boston.redhat.com> <200708101728.30489.paul@codesourcery.com> <1186766002.11930.22.camel@localhost.localdomain> <46BCB48A.9050408@codemonkey.ws> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 10/08/07, Anthony Liguori wrote: > Jeremy Katz wrote: > > On Fri, 2007-08-10 at 17:28 +0100, Paul Brook wrote: > > > >> On Thursday 09 August 2007, Jeremy Katz wrote: > >> > >>> The attached adds a PCI subsystem vendor ID of 0x514D (QM ascii->hex) > >>> for the Cirrus emulation so that you can tell that the system is running > >>> under qemu. This will make it so that, eg, we can detect that in X and > >>> know that resolutions > 800x600 won't blow up a monitor. > >>> > >> I'd rather not. If you want autodetection to work then implement vesa DDC > >> emulation. > >> > > > > The Cirrus hardware never supported it, so it's basically going to be > > making up all new code for the emulation, the drivers, etc. For > > basically dead end emulation, this seems a bit overkill. Especially as > > subsystem vendor/device ids are strongly recommended anyway by the PCI > > spec (though not required) > > > > Longer term, getting emulation of more capable video chipsets is the > > better answer (including DDC or some of the stuff that the VMware SVGA > > adapter supports for passing information back and forth). > > > > QEMU already supports the VMware SVGA adapter nicely but the issue is > that AFAIK the Windows driver is not licensed in such a way that it > could be utilized for QEMU. I believe Ms Windows now ships with the VMware SVGA driver of its own. For reactOS the X driver should be partially reusable. Regards, Andrzej (away until mid-September(?))