<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/conf/machine/qemux86-64.conf, branch thud-20.0.2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=thud-20.0.2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=thud-20.0.2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2018-10-18T22:26:35+00:00</updated>
<entry>
<title>qemux86/gstreamer: Move kernel module recommendation to the machine configuration</title>
<updated>2018-10-18T22:26:35+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2018-10-18T10:15:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=52f1041e1a99d391d954f138589cef497a143cb1'/>
<id>urn:sha1:52f1041e1a99d391d954f138589cef497a143cb1</id>
<content type='text'>
If you try to build a system with multiple BSPs, one of which is qemux86
or qemux86-64, the gstreamer package will change.  This will trigger
anything using gstream to also be rebuilt.

For a package based system, the PR values will also be incremented each
time.  The end result will be an ever growing set of PR values as well as
being unable to tell which configured version of the multimedia components
are really being deployed.

These therefore belong in the machine configuration.

(From OE-Core rev: 112775995158cf6c504fd6beef345ee446f4f11d)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemux86*: Add U-Boot machine configuration</title>
<updated>2018-07-18T09:18:42+00:00</updated>
<author>
<name>Marek Vasut</name>
<email>marex@denx.de</email>
</author>
<published>2018-07-11T15:03:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=48d10a0a91a3f6fa160da3230172fb1a64329d3c'/>
<id>urn:sha1:48d10a0a91a3f6fa160da3230172fb1a64329d3c</id>
<content type='text'>
Add U-Boot machine configuration for the qemux86 and qemux86-64
to allow building U-Boot on those targets. This in turn allows
the auto-updater to update the U-Boot recipe.

(From OE-Core rev: c9bd7f71b59e1c8e7436d65cd8ad6bfb29051c93)

Signed-off-by: Marek Vasut &lt;marex@denx.de&gt;
Cc: Alexander Kanavin &lt;alexander.kanavin@linux.intel.com&gt;
Cc: Otavio Salvador &lt;otavio@ossystems.com.br&gt;
Cc: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Cc: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemux86*: change default wic wks to qemux86-directdisk</title>
<updated>2018-06-04T14:15:00+00:00</updated>
<author>
<name>Anuj Mittal</name>
<email>anuj.mittal@intel.com</email>
</author>
<published>2018-05-31T04:34:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=693638fd5dc46369a58e4913c5a70bf23e82ce17'/>
<id>urn:sha1:693638fd5dc46369a58e4913c5a70bf23e82ce17</id>
<content type='text'>
When runqemu is invoked with an image type (wic, hddimg etc) as a parameter,
the kernel value and command line parameters from qemuboot.conf
are ignored and not passed to qemu cmdline.

As an example, when using:

$ runqemu wic kvm

It results in no network interface and video mode warnings when qemu is up because
the -kernel and -append options were not passed.

Change qemu conf to use qemux86-directdisk.wks that supplies the kernel parameters
that are appended to the bootloader configuration when generating qemu wic
images instead of relying on qemuboot.conf.

Fixes [YOCTO #12224]

(From OE-Core rev: 3b79d9a78816d2eb70fe54ca6cd086d94c115f05)

Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemu conf: Fix kernel module autoloading for uvesafb on genericx86</title>
<updated>2017-09-13T21:07:42+00:00</updated>
<author>
<name>Alejandro Hernandez</name>
<email>alejandro.hernandez@linux.intel.com</email>
</author>
<published>2017-09-07T18:30:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d892af43aaba6ba402c97c72c40f2a41202bf886'/>
<id>urn:sha1:d892af43aaba6ba402c97c72c40f2a41202bf886</id>
<content type='text'>
After commit e8b1c653946ef921b65d47e52aea0dc530ef4286, we started seeing
errors like the following during boot on genericx86 machines:

uvesafb: failed to execute /sbin/v86d
uvesafb: probe of uvesafb.0 failed with error -22
uvesafb: vbe_init() failed with -22
uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2)

These were caused because the uvesa module was being loaded during boot,
when it is only meant to be loaded on qemu according to:
6af89812e8a9931ffed63768ed85367519bf7aef

Since genericx86-common.inc includes qemuboot-x86, the module also tries
to be loaded on genericx86 machines, this patch removes the instruction from
qemuboot-x86 and adds it in specific to both qemux86 machines confs so
it is correctly loaded only on those.

[YOCTO #11879]

(From OE-Core rev: 261f9c382121c73b72556a151fdd4c7938b32a92)

(From OE-Core rev: 554903483acb4af402feaba013366388db89e36b)

Signed-off-by: Alejandro Hernandez &lt;alejandro.hernandez@linux.intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemux86 qemux86-64: Enable pci</title>
<updated>2017-08-09T08:24:15+00:00</updated>
<author>
<name>He Zhe</name>
<email>zhe.he@windriver.com</email>
</author>
<published>2017-07-31T13:11:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f63cb62db45df3b52bd412f02c0cbc7f7e29a330'/>
<id>urn:sha1:f63cb62db45df3b52bd412f02c0cbc7f7e29a330</id>
<content type='text'>
lspci and some other software require "pci" in MACHINE_FEATURES and PCI
is valid in the qemux86* context.

(From OE-Core rev: aec9a159dbc7a78953da73ba9dfccc9e9c9514a7)

Signed-off-by: He Zhe &lt;zhe.he@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemux86*.conf: changed dependency task for syslinux</title>
<updated>2017-04-10T22:00:43+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2017-04-06T14:48:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=88cd926de2894da7f13e5039c1d9cff4a4181280'/>
<id>urn:sha1:88cd926de2894da7f13e5039c1d9cff4a4181280</id>
<content type='text'>
Changed dependency task for syslinux from do_build to
do_populate_sysroot as do_build dependency caused conflicts in
populating image recipe sysroot using conflicting recipes. This
makes do_image_wic task to fail with FileExistsError trying to
copy the same file from two conflicting recipes.

This should also speed up image creation a bit as do_populate_sysroot
task is faster than do_build.

[YOCTO #11295]

(From OE-Core rev: b7bb02901b7002641a8e8cc3fc0b6ec31e5a21f7)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Use weak assignment for SERIAL_CONSOLES in qemu configuration files</title>
<updated>2016-12-13T22:55:20+00:00</updated>
<author>
<name>Chen Qi</name>
<email>Qi.Chen@windriver.com</email>
</author>
<published>2016-12-09T07:43:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=934afbbf90ed07aafdf62bfc01129442b77f4ca8'/>
<id>urn:sha1:934afbbf90ed07aafdf62bfc01129442b77f4ca8</id>
<content type='text'>
Use weak assignment for SERIAL_CONSOLES in qemu configuration files so that
the value could serve as a default value and could be easily overridden in
configuration files like local.conf.

When using the default value for SERIAL_CONSOLES in qemux86-64,we would have
annoying messages on console complaining about respawning getty on ttyS1.
Although the value is set by purpose, at least we need to provide an easy way
to override it.

(From OE-Core rev: 5f060b66162c41a295995947b918253450870117)

Signed-off-by: Chen Qi &lt;Qi.Chen@windriver.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>selftest: wic: fix test_qemu</title>
<updated>2016-12-07T10:38:06+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2016-12-02T23:48:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1b32c6ed025745cb06b7c28ca0fe9e416ce7abfa'/>
<id>urn:sha1:1b32c6ed025745cb06b7c28ca0fe9e416ce7abfa</id>
<content type='text'>
Setting WKS_FILE variable in qemux86-64 made wic test to
use wrong wks file to produce an image and resulted in
test_qemu failure.

Used conditional assignment in qemux86-64 and explicitly
set WKS_FILE in wic testing suite to make the suite to use
wic-image-minimal.wsk. This should fix test_qemu failure.

(From OE-Core rev: 3bca4d18c2712e3b154bacfb917f0a749ebaddeb)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemux86*.conf: set wic-related parameters</title>
<updated>2016-11-30T15:48:07+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2016-11-24T14:40:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8a00c404ab7717c50bc43d12b78bede1d68c109e'/>
<id>urn:sha1:8a00c404ab7717c50bc43d12b78bede1d68c109e</id>
<content type='text'>
Set directdisk.wks as default wks to use for qemux86 machines.
Set requried dependeincies to build directdisk image.

This should simplify building wic images for qemux86* machines.
It should be enough to add wic to the list of IMAGE_FSTYPES to get
the images built.

[YOCTO #10637, YOCTO #8719]

(From OE-Core rev: 8716b8b9be05e3f140bfa426a8e0d4eeaa2edcbe)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>conf: Use xf86-input-libinput by default</title>
<updated>2016-11-01T10:05:45+00:00</updated>
<author>
<name>Jussi Kukkonen</name>
<email>jussi.kukkonen@intel.com</email>
</author>
<published>2016-10-26T08:37:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a1668c8721709f3d1bc0078737514111e1985bdd'/>
<id>urn:sha1:a1668c8721709f3d1bc0078737514111e1985bdd</id>
<content type='text'>
Don't install legacy X input drivers for any machines by default,
RRECOMMEND xf86-input-libinput instead.

This is the setup suggested by upstream: install only libinput by
default, but let niche legacy drivers sort higher in configuration
so they get chosen if installed. So the order is:
 evdev &lt; libinput &lt; (synaptics|vmmouse|...)

This also removes vmmouse X driver from the qemu config. If a VMware
virtual mouse device really needs to be supported, we should enable
CONFIG_MOUSE_PS2_VMMOUSE in kernel instead: that is directly supported
by the libinput X driver.

Fixes [YOCTO #10195].

(From OE-Core rev: 2d005faff6341a81a2afae28860101ba9db51ae8)

Signed-off-by: Jussi Kukkonen &lt;jussi.kukkonen@intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
