qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Uri Lublin" <uril@redhat.com>,
	"Søren Sandmann" <soren.sandmann@gmail.com>,
	"Yonit Halperin" <yhalperi@redhat.com>,
	qemu-devel@nongnu.org, "Arnon Gilboa" <agilboa@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qxl: use correct rom size for revision < 4
Date: Sun, 23 Dec 2012 22:33:39 +0200	[thread overview]
Message-ID: <20121223203339.GC7485@garlic> (raw)
In-Reply-To: <50C9E9A2.7090102@redhat.com>

On Thu, Dec 13, 2012 at 03:43:46PM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> >> That is indeed a better solution, but it does change functionality. I
> >> think it is correct but I'd like to get some other opinions - Uri,
> >> Arnon, Yonit, Soren - any problems with dropping these?
> >>
> > Orientation is used in the Windows Display driver. It is used to set
> > dmDisplayOrientation in DEVMODEW structure
> > (http://msdn.microsoft.com/en-us/library/windows/hardware/ff552837(v=vs.85).aspx).
> 
> What is supposed to happen in case the guest picks a mode with
> orientation != 0?
> 
> > So, I'm not sure we can just drop it. Moreover, we need at least 2 of
> > the orientations, one for AxB resolution and the other for BxA.
> 
> How do I switch a windows guest into 600x800?

AFAIR it is just another mode that appears in the mode list, i.e. when
enumerating the modes via the windows API or via the GUI.

> 
> cheers,
>   Gerd
> 
> 

  reply	other threads:[~2012-12-23 20:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 15:41 [Qemu-devel] [PATCH] qxl: use correct rom size for revision < 4 Alon Levy
2012-12-12 11:46 ` Gerd Hoffmann
2012-12-13 10:40   ` Alon Levy
2012-12-13 14:30     ` Yonit Halperin
2012-12-13 14:43       ` Gerd Hoffmann
2012-12-23 20:33         ` Alon Levy [this message]
2013-01-03  7:55           ` Gerd Hoffmann
2012-12-13 11:36   ` [Qemu-devel] [PATCH 1/2] qxl: stop using non revision 4 rom fields " Alon Levy
2012-12-13 11:36     ` [Qemu-devel] [PATCH 2/2] qxl: change rom so that 4096 < size < 8192 Alon Levy
2012-12-13 12:05       ` Gerd Hoffmann
2012-12-23 20:31         ` Alon Levy
2013-01-15 13:34           ` Alon Levy
2013-01-15 15:19             ` Gerd Hoffmann
2013-01-16 17:59               ` [Qemu-devel] [PATCH v2 0/2] fix two revision related errors Alon Levy
2013-01-16 17:59                 ` [Qemu-devel] [PATCH v2 1/2] qxl: stop using non revision 4 rom fields for revision < 4 Alon Levy
2013-01-16 17:59                 ` [Qemu-devel] [PATCH v2 2/2] qxl: change rom size to 8192 Alon Levy
2013-01-17 13:02                 ` [Qemu-devel] [PATCH v2 0/2] fix two revision related errors Gerd Hoffmann
2013-01-17 13:28                   ` Alon Levy
2013-01-17 13:44                     ` Gerd Hoffmann
2013-01-20 16:30                   ` Alon Levy
2013-01-21  6:26                     ` Gerd Hoffmann
2013-01-21 12:47                   ` Alon Levy
2013-01-21 12:48                   ` [Qemu-devel] [PATCH v3 1/2] qxl: stop using non revision 4 rom fields for revision < 4 Alon Levy
2013-01-21 12:48                     ` [Qemu-devel] [PATCH v3 2/2] qxl: change rom size to 8192 Alon Levy

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=20121223203339.GC7485@garlic \
    --to=alevy@redhat.com \
    --cc=agilboa@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=soren.sandmann@gmail.com \
    --cc=uril@redhat.com \
    --cc=yhalperi@redhat.com \
    /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).