From: David Gibson <david@gibson.dropbear.id.au>
To: Alexander Graf <agraf@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] can we update QEMU's version of u-boot.e500 ?
Date: Fri, 4 Jan 2019 16:03:01 +1100 [thread overview]
Message-ID: <20190104050301.GB2801@umbus.fritz.box> (raw)
In-Reply-To: <9b211327-06a8-9739-e984-4b05557c12b4@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Fri, Jan 04, 2019 at 12:44:59AM +0100, Alexander Graf wrote:
>
>
> On 03.01.19 18:38, Peter Maydell wrote:
> > Hi; currently we ship with a u-boot.e500 which is from u-boot
> > v2017.07. It would be nice to move that forward, specifically
> > to at least v2017.11, which contains upstream u-boot's part of the
> > fix for https://bugs.launchpad.net/qemu/+bug/1714750 .
> > (There are more recent releases than that; it's just the first
> > that contains the fix.)
> >
> > Then we could remove the workaround in scripts/make-release and
> > close out the bug.
> >
> > I've cc'd David as the current maintainer of pc-bios/u-boot.e500
> > and Alex as the last person who did an update.
>
> I think it's a great idea to update it.
>
> David, do you want to do that or rather have me send a patch?
Please send a patch.
I'm maintainer of all the ppc boards by default, but I really don't
know anything much about e500 or u-boot.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-04 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 17:38 [Qemu-devel] can we update QEMU's version of u-boot.e500 ? Peter Maydell
2019-01-03 23:44 ` Alexander Graf
2019-01-04 5:03 ` David Gibson [this message]
2019-02-28 13:23 ` Peter Maydell
2019-03-04 8:38 ` David Gibson
2019-03-04 10:41 ` Alexander Graf
2019-03-04 10:48 ` Daniel P. Berrangé
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=20190104050301.GB2801@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=peter.maydell@linaro.org \
--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).