From: Gerd Hoffmann <kraxel@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] commit 56bd9ea1a breaks display
Date: Mon, 15 Sep 2014 08:27:22 +0200 [thread overview]
Message-ID: <1410762442.23112.6.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <alpine.LMD.2.02.1409131125300.24968@jedlik.phy.bme.hu>
On Sa, 2014-09-13 at 11:30 +0200, BALATON Zoltan wrote:
> Hello,
>
> It looks like that commit 56bd9ea1a37395012adecca8b9c4762da15b01e7
> (console: reimplement qemu_default_pixelformat) breaks display with
> qemu-system-ppc on x86_64 host with SDL. The window just stays black after
> this commit (although the machine still runs, it cannot be seen). Can you
> check please?
Must be something in SDL. gtk works, and vnc works too.
I'll have a look.
cheers,
Gerd
prev parent reply other threads:[~2014-09-15 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 9:30 [Qemu-devel] commit 56bd9ea1a breaks display BALATON Zoltan
2014-09-15 6:27 ` Gerd Hoffmann [this message]
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=1410762442.23112.6.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=balaton@eik.bme.hu \
--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).