qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Katz <katzj@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH/RFC] Set a (distinguishable) subsystem id for Cirrus VGA
Date: Fri, 10 Aug 2007 13:13:22 -0400	[thread overview]
Message-ID: <1186766002.11930.22.camel@localhost.localdomain> (raw)
In-Reply-To: <200708101728.30489.paul@codesourcery.com>

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

  reply	other threads:[~2007-08-10 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 19:27 [Qemu-devel] [PATCH/RFC] Set a (distinguishable) subsystem id for Cirrus VGA Jeremy Katz
2007-08-10 16:28 ` Paul Brook
2007-08-10 17:13   ` Jeremy Katz [this message]
2007-08-10 18:16     ` Paul Brook
2007-08-10 18:55     ` Anthony Liguori
2007-08-10 22:47       ` WaxDragon
2007-08-11 17:14       ` andrzej zaborowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1186766002.11930.22.camel@localhost.localdomain \
    --to=katzj@redhat.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).