From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: BALATON Zoltan <balaton@eik.bme.hu>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] ppc vga output breakage since commit c3c1bb99
Date: Sat, 28 Mar 2015 19:19:58 +0000 [thread overview]
Message-ID: <5516FEDE.3030809@ilande.co.uk> (raw)
In-Reply-To: <alpine.GSO.2.01.1503281955530.6055@mono>
On 28/03/15 19:04, BALATON Zoltan wrote:
> Hello,
>
> Commit c3c1bb99d1c11978d9ce94d1bdcf0705378c1459 (exec: Respect
> as_tranlsate_internal length clamp) seems to break vga output with
> qemu-system-ppc on x86_64 host. Since this commit, the output window
> does not get to the OpenBIOS console but stays black. (Easy to reproduce
> by just starting qemu-system-ppc.)
>
> The reason may be that this change has exposed another bug somewhere
> else but this is all quite obscure to me. Does anyone have any idea what
> could be wrong or where to look further. Any help is appreciated.
Hi Zoltan,
Yes indeed, this has been picked up in the last few days and is on the
list of issues to be dealt with for -rc2. So watch this space...
ATB,
Mark.
next prev parent reply other threads:[~2015-03-28 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 19:04 [Qemu-devel] ppc vga output breakage since commit c3c1bb99 BALATON Zoltan
2015-03-28 19:19 ` Mark Cave-Ayland [this message]
2015-03-30 9:51 ` Paolo Bonzini
2015-03-30 10:20 ` Mark Cave-Ayland
2015-03-30 10:28 ` Paolo Bonzini
2015-03-30 11:45 ` Peter Crosthwaite
2015-03-30 11:47 ` Paolo Bonzini
2015-03-31 22:34 ` Mark Cave-Ayland
2015-04-01 7:55 ` Paolo Bonzini
2015-04-02 11:45 ` Mark Cave-Ayland
2015-04-02 13:53 ` Paolo Bonzini
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=5516FEDE.3030809@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=balaton@eik.bme.hu \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).