From: "Burton, Ross" <ross.burton@intel.com>
To: Takashi Matsuzawa <tmatsuzawa@xevo.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: genericx86 vs qemux86
Date: Fri, 3 Feb 2017 23:20:27 +0000 [thread overview]
Message-ID: <CAJTo0LZyg6+pD7DKUb9c42=m_G5ngWyoqmxafLvSZP5Xn-JkJA@mail.gmail.com> (raw)
In-Reply-To: <DM5PR0101MB295332119B0A4D1653E73F98B64F0@DM5PR0101MB2953.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On 3 February 2017 at 23:16, Takashi Matsuzawa <tmatsuzawa@xevo.com> wrote:
> Sorry, I am still a bit confused with genericx86 and qemux86 targets.
> What is their difference and which one to choose.
> Both are x86 target and maybe genericx86 has more support for PC hardware?
> qemux86 has v86d?
> genericx86 is from poky and qemux86 is from openembeded?
>
qemux86 is specifically for use in qemu, so it targets a CPU that qemu is
good at executing and has the virtualised hardware drivers in. genericx86
is an attempt at a "all purpose" x86 machine that runs most places
acceptably.
My recommendation would be to use qemux86 (-64) for virtual environments
and a machine from meta-intel (intel-corei7-64 or intel-core2-32) for real
hardware. The genericx86 machine, being part of poky, is basically for QA
purposes and if you are targetting Intel hardware then the Intel BSPs are
better.
Ross
[-- Attachment #2: Type: text/html, Size: 1375 bytes --]
next prev parent reply other threads:[~2017-02-03 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 23:16 genericx86 vs qemux86 Takashi Matsuzawa
2017-02-03 23:20 ` Burton, Ross [this message]
2017-02-04 3:59 ` Takashi Matsuzawa
2017-02-04 13:38 ` 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='CAJTo0LZyg6+pD7DKUb9c42=m_G5ngWyoqmxafLvSZP5Xn-JkJA@mail.gmail.com' \
--to=ross.burton@intel.com \
--cc=tmatsuzawa@xevo.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.