From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] PPC heathrow broken - update OpenBIOS to r1063?
Date: Mon, 27 Aug 2012 23:13:03 +0200 [thread overview]
Message-ID: <20120827211303.GA16996@ohm.aurel32.net> (raw)
Hi,
As you probably know, the PPC machines with a heathrow controller is
broken following commit 9e56edcf ("vga: raise default vgamem size").
The PCI hole space is not big enough for such a new default size.
Alexander has fixed it in OpenBIOS r1063, while the current version in
QEMU is r1062. It would be nice if OpenBIOS PPC could be updated in git.
Do we want to keep the SPARC version in sync? Should I do it?
Regards,
Aurelien
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next reply other threads:[~2012-08-27 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 21:13 Aurelien Jarno [this message]
2012-08-28 0:59 ` [Qemu-devel] PPC heathrow broken - update OpenBIOS to r1063? Alexander Graf
2012-08-28 18:41 ` Aurelien Jarno
2012-08-28 16:55 ` Blue Swirl
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=20120827211303.GA16996@ohm.aurel32.net \
--to=aurelien@aurel32.net \
--cc=agraf@suse.de \
--cc=blauwirbel@gmail.com \
--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).