All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Sakib Sajal <sakib.sajal@windriver.com>,
	 openembedded-core@lists.openembedded.org
Cc: Joe Slater <joe.slater@windriver.com>
Subject: Re: [OE-core][PATCH V2] qemu: uprev v4.2.0 -> v5.0.0
Date: Mon, 22 Jun 2020 22:00:09 +0100	[thread overview]
Message-ID: <c954295945368b13368ea14ff92a025a21d207a2.camel@linuxfoundation.org> (raw)
In-Reply-To: <161AEE4AD64EFA55.6387@lists.openembedded.org>

On Mon, 2020-06-22 at 18:36 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Fri, 2020-06-19 at 14:12 -0400, Sakib Sajal wrote:
> > Major update after v4.2.
> > 
> > Changes:
> >   - os_find_datadir() was changed after the v4.2 release
> >     causing v5.0 to not find the bios and not boot the
> >     image. Fix is sent to upstream qemu.
> >     See: qemu/find_datadir.patch
> >   - v5.0 binary had host contamination for dynamically linked
> >     libraries, "--extra-ldflags='${LDFLAGS}'" in EXTRA_OECONF
> >     resolved the issue
> >   - bluetooth code was removed: qemu.git$ git show 1d4ffe8dc7
> >     hence removed PACKAGECONFIG[bluez]
> >   - -show-cursor qemu option is now deprecated, updated
> >     scripts/runqemu to use updated option instead
> >   - added PACKAGECONFIG definitions
> >   - added qemu-ptest to conf/distro/include/ptest-packagelists.inc
> >   - increased support for ARM architecture, cpu and board
> >   - removed patches merged upstream and refreshed
> >     existing ones
> > 
> > Testing:
> > Build core-image-minimal against the machines in
> > openembedded-core/meta/conf/machine and succesfully
> > booted with qemu v5.0
> > 
> > Ran qemu-ptest on x86-64 and arm64 with identical results:
> > PASS: 1166
> > SKIP:    0
> > FAIL:    0
> > 
> > Signed-off-by: Sakib Sajal <sakib.sajal@windriver.com>
> > Signed-off-by: Joe Slater <joe.slater@windriver.com>
> 
> This is in general looking good but we did see one error:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/62/builds/2050
> 
> which is strange as its only on the edgerouter.

Its because qemu can't run on mips machines. We therefore need:

PTESTS_FAST_remove_mips64 = "qemu-ptest"

I can add this as a fixup to the patch.

Cheers,

Richard


  parent reply	other threads:[~2020-06-22 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 18:12 [OE-core][PATCH V2] qemu: uprev v4.2.0 -> v5.0.0 Sakib Sajal
2020-06-22 17:36 ` Richard Purdie
     [not found] ` <161AEE4AD64EFA55.6387@lists.openembedded.org>
2020-06-22 21:00   ` Richard Purdie [this message]
2020-06-22 23:18     ` Sakib Sajal

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=c954295945368b13368ea14ff92a025a21d207a2.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=joe.slater@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sakib.sajal@windriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.