From: Thomas Huth <thuth@redhat.com>
To: Alexander Graf <agraf@suse.de>, qemu-ppc@nongnu.org
Cc: mihai.caraman@freescale.com, qemu-devel@nongnu.org,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] PPC: E500: Update u-boot to commit 79c884d7e4
Date: Fri, 28 Aug 2015 14:00:26 +0200 [thread overview]
Message-ID: <55E04D5A.3050500@redhat.com> (raw)
In-Reply-To: <1440761241-84182-1-git-send-email-agraf@suse.de>
On 28/08/15 13:27, Alexander Graf wrote:
> The current U-Boot binary in QEMU has a bug where it fails to support
> dynamic CCSR addressing. Without this support, u-boot can not boot the
> ppce500 machine anymore. This has been fixed upstream in u-boot commit
> e834975b.
>
> Update the u-boot blob we carry in QEMU to the latest u-boot upstream,
> so that we can successfully run u-boot with the ppce500 machine again.
>
> CC: qemu-stable@nongnu.org
> Signed-off-by: Alexander Graf <agraf@suse.de>
This fixes the issue from https://bugs.launchpad.net/qemu/+bug/1481750 !
Tested-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2015-08-28 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 11:27 [Qemu-devel] [PATCH] PPC: E500: Update u-boot to commit 79c884d7e4 Alexander Graf
2015-08-28 12:00 ` Thomas Huth [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=55E04D5A.3050500@redhat.com \
--to=thuth@redhat.com \
--cc=agraf@suse.de \
--cc=mihai.caraman@freescale.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-stable@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).