From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Jeremy Katz <katzj@redhat.com>
Subject: Re: [Qemu-devel] [PATCH/RFC] Set a (distinguishable) subsystem id for Cirrus VGA
Date: Fri, 10 Aug 2007 19:16:02 +0100 [thread overview]
Message-ID: <200708101916.02932.paul@codesourcery.com> (raw)
In-Reply-To: <1186766002.11930.22.camel@localhost.localdomain>
On Friday 10 August 2007, 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.
My sources say otherwise.
The current Xorg cirrus driver clearly has DDC (aka i2c) support, and there's
a patch for linux framebuffer support here: http://lkml.org/lkml/2006/7/4/230
qemu already have a generic i2c framework, and i2c EEPROM devices (used to
hold the EDID), so all you need to implement is the cirrus host bits.
It's not entirely trivial as the card sees to just expose the raw signal
lines. However i2c is fairly straightforward, so it shouldn't be that hard to
implement.
Paul
next prev parent reply other threads:[~2007-08-10 18:16 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
2007-08-10 18:16 ` Paul Brook [this message]
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=200708101916.02932.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=katzj@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.