Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 02/12] qemu: switch to '-vga std' emulated hardware from vmware/cirrus for x86/mips
Date: Fri, 23 Aug 2019 10:13:21 +0100	[thread overview]
Message-ID: <a1afd589e5a20fa0fa780b2290e75caedbbf17d8.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190820153219.62435-2-alex.kanavin@gmail.com>

On Tue, 2019-08-20 at 17:32 +0200, Alexander Kanavin wrote:
> This is the qemu default since qemu 2.2, is generally supported
> better,
> and is recommended by upstream. It also has already been in use for
> arm/risc
> and ovmf.
> 
> Additional information:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13466
> https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/
> 
> '-vga virtio' emulated hardware remains in use when virgl is enabled
> via a runqemu override.
> 
> Also, adjust the error whitelist, as there is a number of new
> messages
> coming from the drivers that are not actual errors.
> 
> Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
> ---
>  meta/conf/machine/include/qemuboot-mips.inc | 2 +-
>  meta/conf/machine/include/qemuboot-x86.inc  | 2 +-
>  meta/conf/machine/qemux86-64.conf           | 1 +
>  meta/conf/machine/qemux86.conf              | 1 +
>  meta/lib/oeqa/runtime/cases/parselogs.py    | 5 ++++-
>  scripts/runqemu                             | 6 ------
>  6 files changed, 8 insertions(+), 9 deletions(-)

The patches in master-next had some failures:

https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/636

I think but am not 100% sure it could from this patch?

Cheers,

Richard



  reply	other threads:[~2019-08-23  9:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 15:32 [PATCH 01/12] linux-yocto: add drm-bochs support Alexander Kanavin
2019-08-20 15:32 ` [PATCH 02/12] qemu: switch to '-vga std' emulated hardware from vmware/cirrus for x86/mips Alexander Kanavin
2019-08-23  9:13   ` Richard Purdie [this message]
2019-08-23 10:34     ` Alexander Kanavin
2019-08-20 15:32 ` [PATCH 03/12] images: use 512M of RAM in qemu if 'opengl" is in DISTRO_FEATURES Alexander Kanavin
2019-08-20 15:32 ` [PATCH 04/12] python3-numpy: update to 1.17.0 Alexander Kanavin
2019-08-22 13:33   ` Richard Purdie
2019-08-22 15:07     ` Alexander Kanavin
2019-08-20 15:32 ` [PATCH 05/12] rt-tests: exclude another development version Alexander Kanavin
2019-08-20 15:32 ` [PATCH 06/12] libmodulemd: depend on target python at build time Alexander Kanavin
2019-08-20 15:32 ` [PATCH 07/12] createrepo-c: upgrade 0.14.3 -> 0.15.0 Alexander Kanavin
2019-08-20 15:32 ` [PATCH 08/12] gtk-doc: upgrade 1.30 -> 1.31 Alexander Kanavin
2019-08-20 15:32 ` [PATCH 09/12] desktop-file-utils: upgrade 0.23 -> 0.24 Alexander Kanavin
2019-08-20 15:32 ` [PATCH 10/12] vala: upgrade 0.44.5 -> 0.44.7 Alexander Kanavin
2019-08-20 15:32 ` [PATCH 11/12] libdazzle: upgrade 3.32.2 -> 3.32.3 Alexander Kanavin
2019-08-20 15:32 ` [PATCH 12/12] epiphany: upgrade 3.32.3 -> 3.32.4 Alexander Kanavin

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=a1afd589e5a20fa0fa780b2290e75caedbbf17d8.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.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