From: Tom Rini <trini@konsulko.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 1/4] tools: docker: Bump up QEMU version to 6.1.0
Date: Wed, 25 Aug 2021 19:04:28 -0400 [thread overview]
Message-ID: <20210825230428.GG858@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmVFaVD96qFCEpcuz6nixCDV-zXsdBfP5EKpdRFpNxr-fA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
On Wed, Aug 25, 2021 at 01:00:46PM +0800, Bin Meng wrote:
> On Wed, Aug 25, 2021 at 10:01 AM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Wed, Aug 25, 2021 at 08:05:17AM +0800, Bin Meng wrote:
> >
> > > At present U-Boot CI testing is still using QEMU 4.2.0 which is
> > > pretty old. Let's bump up to QEMU 6.1.0.
> > >
> > > ninja-build is added as the prerequisite required by QEMU 6.1.0.
> > >
> > > Note there is a bug in QEMU 6.1.0 Xilinx Zynq UART emulation codes.
> > > A quick fix [1] was posted on QEMU mailing list but it it too late
> > > for 6.1.0 release. Hence my custom repo is used that contains this
> > > fix on top of the v6.1.0 release tag at the time being. We should
> > > switch to QEMU official repo once the fix is merged in next release.
> > >
> > > [1] http://patchwork.ozlabs.org/project/qemu-devel/patch/20210823020813.25192-2-bmeng.cn@gmail.com/
> >
> > Can we cherry-pick this from upstream? How long is it likely to take
> > before say 6.1.1 is out?
>
> There is probably no 6.1.1 per QEMU release cadence. The fix has not
> been applied yet, so we cannot cherry pick it up now.
>
> If using a custom repo is a problem, how about "wget <patch> from
> patchwork" and "git am" on top of the official repo?
Yeah, I think that would be a good alternative.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2021-08-25 23:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 0:05 [PATCH 1/4] tools: docker: Bump up QEMU version to 6.1.0 Bin Meng
2021-08-25 0:05 ` [PATCH 2/4] tools: docker: Build and install genimage Bin Meng
2021-08-25 2:00 ` Tom Rini
2021-08-25 0:05 ` [PATCH 3/4] riscv: sifive: unleashed: Add genimage config files Bin Meng
2021-08-25 0:05 ` [PATCH 4/4] azure/gitlab: Add tests for SiFive Unleashed board Bin Meng
2021-08-25 2:01 ` [PATCH 1/4] tools: docker: Bump up QEMU version to 6.1.0 Tom Rini
2021-08-25 5:00 ` Bin Meng
2021-08-25 23:04 ` Tom Rini [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=20210825230428.GG858@bill-the-cat \
--to=trini@konsulko.com \
--cc=bmeng.cn@gmail.com \
--cc=u-boot@lists.denx.de \
/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