From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IJY5J-0004Rc-Ka
	for qemu-devel@nongnu.org; Fri, 10 Aug 2007 13:15:37 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IJY5H-0004Ps-JL
	for qemu-devel@nongnu.org; Fri, 10 Aug 2007 13:15:37 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IJY5H-0004Ph-CT
	for qemu-devel@nongnu.org; Fri, 10 Aug 2007 13:15:35 -0400
Received: from mx1.redhat.com ([66.187.233.31])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <katzj@redhat.com>) id 1IJY5H-0007nI-08
	for qemu-devel@nongnu.org; Fri, 10 Aug 2007 13:15:35 -0400
Subject: Re: [Qemu-devel] [PATCH/RFC] Set a (distinguishable) subsystem id
	for Cirrus VGA
From: Jeremy Katz <katzj@redhat.com>
In-Reply-To: <200708101728.30489.paul@codesourcery.com>
References: <1186687670.26986.19.camel@erebor.boston.redhat.com>
	<200708101728.30489.paul@codesourcery.com>
Content-Type: text/plain
Date: Fri, 10 Aug 2007 13:13:22 -0400
Message-Id: <1186766002.11930.22.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org

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).  

Jeremy