From: Patrick Ohly <patrick.ohly@intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: x86 testing
Date: Wed, 18 Jan 2017 10:19:14 +0100 [thread overview]
Message-ID: <1484731154.19478.117.camel@intel.com> (raw)
In-Reply-To: <48565564-9e2f-f8e7-e3da-21aad9fca0a3@mlbassoc.com>
On Wed, 2017-01-18 at 08:02 +0100, Gary Thomas wrote:
> I'm trying to track down some recent changes in the X server
> (using the latest Poky/Yocto master). I've had failures on
> a number of the embedded targets I work with, so I thought
> I'd give it a go on platforms with a larger base - x86 machines.
>
> It used to be that I could run qemu and it would pop up a separate
> window that emulated a display+keyboard+mouse. That doesn't seem
> to be the same now, or at least I don't see how to make it work.
qemu-native was changed to not depend on SDL. Instead of opening its own
window, it now provides access via VNC.
If you want the old behavior back, you need to compile with (from Poky's
local.conf.sample):
# By default qemu will build with a builtin VNC server where graphical output can be
# seen. The two lines below enable the SDL backend too. By default libsdl-native will
# be built, if you want to use your host's libSDL instead of the minimal libsdl built
# by libsdl-native then uncomment the ASSUME_PROVIDED line below.
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
#ASSUME_PROVIDED += "libsdl-native"
> Advice on this would be great as I need to test the "native" X
> setup, not VNC connections.
For the guest OS it shouldn't make a difference whether qemu uses its
own window or VNC.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-01-18 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 7:02 x86 testing Gary Thomas
2017-01-18 9:19 ` Patrick Ohly [this message]
2017-01-18 9:20 ` Jussi Kukkonen
2017-01-18 9:23 ` Burton, Ross
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=1484731154.19478.117.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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 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.