All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-ppc@nongnu.org,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc]  PPC: VGA broken in git master
Date: Mon, 05 Mar 2012 11:29:56 +0100	[thread overview]
Message-ID: <4F5495A4.5030502@suse.de> (raw)
In-Reply-To: <4F548CBD.5030308@redhat.com>

On 03/05/2012 10:51 AM, Avi Kivity wrote:
> On 03/04/2012 08:06 PM, Mark Cave-Ayland wrote:
>> Hi all,
>>
>> I've just done a git pull to update my local repository, and it now
>> appears that the VGA device is broken in QEMU - rather than displaying
>> the OpenBIOS banner in my VNC client, the framebuffer remains
>> constantly black.
>>
>> A git bisect shows that the problem is caused by the following commit:
>>
>>
>> de58ac72b6a062d1a61478284c0c0f8a0428613e is the first bad commit
>> commit de58ac72b6a062d1a61478284c0c0f8a0428613e
>> Author: Avi Kivity<avi@redhat.com>
>> Date:   Sun Jan 8 19:46:17 2012 +0200
>>
>>      ioport: change portio_list not to use memory_region_set_offset()
>>
>>      memory_region_set_offset() will be going away soon, so don't use it.
>>      Use an alias instead.
>>
>>      Signed-off-by: Avi Kivity<avi@redhat.com>
>>      Reviewed-by: Richard Henderson<rth@twiddle.net>
>>
>>
>> Avi/Richard - please would it be possible for you to review this
>> commit and come up with a suitable fix?
>>
> Can you provide the command line needed to reproduce the problem?

 From the bug description I would say:

$ ./qemu-system-ppc


Alex

      parent reply	other threads:[~2012-03-05 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 18:06 [Qemu-devel] PPC: VGA broken in git master Mark Cave-Ayland
2012-03-05  9:51 ` Avi Kivity
2012-03-05 10:29   ` Mark Cave-Ayland
2012-03-05 15:48     ` Avi Kivity
2012-03-05 16:16       ` Mark Cave-Ayland
2012-03-05 18:50         ` Alon Levy
2012-03-05 10:29   ` Alexander Graf [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=4F5495A4.5030502@suse.de \
    --to=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --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 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.