From: Jan Kiszka <jan.kiszka@web.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
X86 <xen-devel@lists.xensource.com>,
Igor Mitsyanko <i.mitsyanko@samsung.com>,
Evgeny Voevodin <e.voevodin@samsung.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
qemu-devel@nongnu.org, Dmitry Solodkiy <d.solodkiy@samsung.com>,
Maksim Kozlov <m.kozlov@samsung.com>
Subject: Re: [PATCH 16/18] console: stop using DisplayState in gfx hardware emulation
Date: Mon, 25 Mar 2013 08:59:33 +0100 [thread overview]
Message-ID: <515003E5.7000809@web.de> (raw)
In-Reply-To: <51500302.6040506@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
On 2013-03-25 08:55, Gerd Hoffmann wrote:
> On 03/25/13 08:50, Jan Kiszka wrote:
>> On 2013-03-12 11:32, Gerd Hoffmann wrote:
>>> Use QemuConsole instead. Updates interfaces in console.[ch] and
>>> adapts gfx hardware emulation code.
>>
>> Breaks vmware-vga, the X server no longer starts up.
>>
>> I do not spot any obvious typo etc. in the conversion, so I
>> suspect, some values returned by the surface API differ from those
>> that the DisplayState used to provide.
>>
>> Jan
>
> Known issue, fix is queued but not yet merged:
>
> http://patchwork.ozlabs.org/patch/229214/
Nope, I seem to stress something else: No change here after applying
that patch.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-03-25 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1363084369-27517-1-git-send-email-kraxel@redhat.com>
2013-03-12 10:32 ` [PATCH 07/18] console: rework DisplaySurface handling [vga emu side] Gerd Hoffmann
2013-03-12 10:32 ` [PATCH 16/18] console: stop using DisplayState in gfx hardware emulation Gerd Hoffmann
2013-03-25 7:50 ` Jan Kiszka
2013-03-25 7:55 ` Gerd Hoffmann
2013-03-25 7:59 ` Jan Kiszka [this message]
2013-03-25 8:21 ` Gerd Hoffmann
2013-03-25 8:28 ` Jan Kiszka
2013-03-25 8:39 ` Gerd Hoffmann
2013-03-25 8:40 ` Jan Kiszka
2013-03-25 9:10 ` Gerd Hoffmann
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=515003E5.7000809@web.de \
--to=jan.kiszka@web.de \
--cc=aliguori@us.ibm.com \
--cc=d.solodkiy@samsung.com \
--cc=e.voevodin@samsung.com \
--cc=i.mitsyanko@samsung.com \
--cc=kraxel@redhat.com \
--cc=m.kozlov@samsung.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).