From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IJZdi-0005wf-5L for qemu-devel@nongnu.org; Fri, 10 Aug 2007 14:55:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IJZdg-0005wD-PL for qemu-devel@nongnu.org; Fri, 10 Aug 2007 14:55:13 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IJZdg-0005w3-Fa for qemu-devel@nongnu.org; Fri, 10 Aug 2007 14:55:12 -0400 Received: from wr-out-0506.google.com ([64.233.184.229]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IJZdg-0001A3-4y for qemu-devel@nongnu.org; Fri, 10 Aug 2007 14:55:12 -0400 Received: by wr-out-0506.google.com with SMTP id c38so227329wra for ; Fri, 10 Aug 2007 11:55:11 -0700 (PDT) Message-ID: <46BCB48A.9050408@codemonkey.ws> Date: Fri, 10 Aug 2007 13:55:06 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH/RFC] Set a (distinguishable) subsystem id for Cirrus VGA References: <1186687670.26986.19.camel@erebor.boston.redhat.com> <200708101728.30489.paul@codesourcery.com> <1186766002.11930.22.camel@localhost.localdomain> In-Reply-To: <1186766002.11930.22.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Cc: Paul Brook 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 suspect our best long term bet is a new paravirtual graphics driver that's also a standard VESA device and the hope that someone writes a proper Windows driver for it. Regards, Anthony Liguori > Jeremy > > > > >