From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Alexander Graf <agraf@csgraf.de>
Cc: David Gibson <david@gibson.dropbear.id.au>,
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: Mon, 4 Mar 2019 10:48:31 +0000 [thread overview]
Message-ID: <20190304104831.GI4239@redhat.com> (raw)
In-Reply-To: <2909f1ff-4714-50f5-64c6-2a0712510837@csgraf.de>
On Mon, Mar 04, 2019 at 11:41:50AM +0100, Alexander Graf wrote:
>
>
> On 04.03.19 09:38, David Gibson wrote:
> > On Thu, Feb 28, 2019 at 01:23:38PM +0000, Peter Maydell wrote:
> >> On Fri, 4 Jan 2019 at 05:22, David Gibson <david@gibson.dropbear.id.au> wrote:
> >>>
> >>> 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.
> >>
> >> Hi -- any progress on this ? It would be nice to update the u-boot
> >> blob before QEMU hits softfreeze for the next release in a
> >> couple of weeks...
> >
> > It would. If there's been another patch, I haven't seen it though.
>
> I wanted to build that on a PPC machine, but then realized I'd first
> have to set up a PPC VM to actually build on (as the host is LE), and
> that then somehow never happened.
>
> Either way, I set myself up with a local cross compilation setup now, so
> you should ideally have a patch that bumps U-Boot on e500 to 2019.01.
FWIW, qemu source tree includes a dockerfile for cross-builds of QEMU
itself, perhaps it is useful for u-boot builds too:
tests/docker/dockerfiles/debian-ppc64el-cross.docker
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2019-03-04 10:48 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
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é [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=20190304104831.GI4239@redhat.com \
--to=berrange@redhat.com \
--cc=agraf@csgraf.de \
--cc=david@gibson.dropbear.id.au \
--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).