<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/conf/machine/include, branch uninative-2.8</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=uninative-2.8</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=uninative-2.8'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2020-02-28T23:11:29+00:00</updated>
<entry>
<title>tune-cortexa72-cortexa53.inc: Adding missing TUNE_FEATURES</title>
<updated>2020-02-28T23:11:29+00:00</updated>
<author>
<name>Jaewon Lee</name>
<email>jaewon.lee@xilinx.com</email>
</author>
<published>2020-01-23T21:02:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f5803c5ee2c46a062a27254c03a5068ace0fc627'/>
<id>urn:sha1:f5803c5ee2c46a062a27254c03a5068ace0fc627</id>
<content type='text'>
Without the proper default tune in TUNE_FEATURES, certain variables
won't expand correctly. MACHINEOVERRIDES won't add cortexa72-cortexa53:
TUNE_CCARGS won't add -mtune=cortexa72.cortexa-53, generating the toolchain
incorrectly.
Adding missing 'cortexa72-cortexa53' to both
TUNE_FEATURES_tune-cortexa72-cortexa53 and
TUNE_FEATURES_tune-cortexa72-cortexa53-crypto

(From OE-Core rev: eee65bed5ee39051541a0a3f2a311396d6e7326c)

Signed-off-by: Jaewon Lee &lt;jaewon.lee@xilinx.com&gt;
Signed-off-by: Alejandro Enedino Hernandez Samaniego &lt;alejandr@xilinx.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemu: bump default reference kernel to v5.4</title>
<updated>2020-02-22T23:57:27+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2020-02-21T17:46:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=57a6948feac5585f088c23e91142d887184bd18c'/>
<id>urn:sha1:57a6948feac5585f088c23e91142d887184bd18c</id>
<content type='text'>
Now that the 5.4 recipes are available, we bump the default versions
to use them.

(From OE-Core rev: c250dbd2a68048f83837e7cbdfb53bc38623e4a2)

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemumips: use std vga instead of cirrus vga</title>
<updated>2020-02-21T09:39:00+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2020-02-19T19:47:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=fca233e5d424a05dcd19f5385d06d8f62e3e5a17'/>
<id>urn:sha1:fca233e5d424a05dcd19f5385d06d8f62e3e5a17</id>
<content type='text'>
This is what the upstream recommends nowadays:
https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/

I have verified that both X and weston continue to boot and look
right; however xorg.conf file needs to be removed as it is cirrus
specific and doesn't work and isn't needed with std vga.

(From OE-Core rev: 96e6434239268fd0fc021bda9c8fedd998597097)

Signed-off-by: Alexander Kanavin &lt;alex.kanavin@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemux86: drop resolution setting via uvesafb</title>
<updated>2020-02-18T23:53:54+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2020-02-16T15:50:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ec7beb650fd3ad445e77d2c3c8fde27556d9d0c9'/>
<id>urn:sha1:ec7beb650fd3ad445e77d2c3c8fde27556d9d0c9</id>
<content type='text'>
I am not sure if this has ever worked, but uvesafb is a really
outdated (VBE from the 1990s), awkward (needs v86d) and limited
(no support for high resolutions) way to do it.

The specific reason 640x480-32 was introduced (ages ago) was
to force 32 bit mode with vmware driver, as 16bit had rendering issues.

The modern, supported option is video=... kernel parameter documented here:
https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDID
https://github.com/torvalds/linux/blob/master/Documentation/fb/modedb.rst
which can be passed directly to runqemu and doesn't require special
kernel modules.

Sato under X will continue to use 640x480 as that is hardcoded into
xorg.conf under qemu.

(From OE-Core rev: 1cf26f69fd89b43be24cd1232c43e5050b9d718a)

Signed-off-by: Alexander Kanavin &lt;alex.kanavin@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemux86: do not add vga=0 to kernel parameters</title>
<updated>2020-02-18T23:53:54+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2020-02-16T15:50:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e88fe83014b771b1868ee1159672c80f7710f41d'/>
<id>urn:sha1:e88fe83014b771b1868ee1159672c80f7710f41d</id>
<content type='text'>
This was added ages ago to enable GL passthrough with
vmware driver, and is no longer relevant, as std or virgl is used
instead nowadays.

Original commit:

commit 072545b1111c5efb66289a4866897429f5fcd969
Author: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
Date:   Wed Jan 21 17:40:51 2009 +0000

    scripts/poky-qemu-internal: Add support for GL passthrough in qemux86 images

(From OE-Core rev: 857078ba8eda153f4a097683db551a7d310ecc01)

Signed-off-by: Alexander Kanavin &lt;alex.kanavin@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>microblaze tune: cleanup +=</title>
<updated>2020-02-06T12:16:34+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2020-02-04T21:06:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d6b0154a4c1e897d6cd2f815c13ad9d6f34c1355'/>
<id>urn:sha1:d6b0154a4c1e897d6cd2f815c13ad9d6f34c1355</id>
<content type='text'>
Various += were used, refactor these to be either = or .= depending on
usuage.

CONFLICTS should be '=', as no leading space is required and they are not
amending any other conflict settings.

The TUNE_CCARGS should be .= so that if the feature does not define a CCARG
blank spaces are not added to the CFLAGS.  This is consistent to how the arm
tuning is implemented.

(From OE-Core rev: 78c38857486d3107ecd95d0ceefabcf5152c3928)

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
Signed-off-by: Mark Hatle &lt;mark.hatle@kernel.crashing.org&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>microblaze tune: Enable 64-bit</title>
<updated>2020-02-06T12:16:34+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2020-02-04T21:06:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=83e58868b5fcd3846d81ec04f0b7b1751b4ca0d0'/>
<id>urn:sha1:83e58868b5fcd3846d81ec04f0b7b1751b4ca0d0</id>
<content type='text'>
64-bit is not yet available in Linux, but some non-Linux uses exist.

(From OE-Core rev: 389691be34b79da1fafa8df2e6369e7771406cc2)

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
Signed-off-by: Mark Hatle &lt;mark.hatle@kernel.crashing.org&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>microblaze tune: Allow no version to be set</title>
<updated>2020-02-06T12:16:34+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2020-02-04T21:06:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e45c38203378b4bb99cc077f5dad69914cb18137'/>
<id>urn:sha1:e45c38203378b4bb99cc077f5dad69914cb18137</id>
<content type='text'>
We want to allow no version to be configured.  This should use the GCC default
which is the latest defined version, currently 11.0.

(From OE-Core rev: 0d1551dcc169f2d8dbfbe01b4f1f0ae3ce4770ed)

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
Signed-off-by: Mark Hatle &lt;mark.hatle@kernel.crashing.org&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>microblaze tune: change microblazeeb to microblaze</title>
<updated>2020-02-06T12:16:34+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2020-02-04T21:06:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7f150a2514cf6ca69b7cb9b5acbaac86f714b9ec'/>
<id>urn:sha1:7f150a2514cf6ca69b7cb9b5acbaac86f714b9ec</id>
<content type='text'>
Using microblazeeb breaks a number of autoconf recipes, including newlib
components.  'microblaze' is defined as the big-endian version, while
microblazeel is defined as the little-endian version.

config.sub: 2018-07-03

...
        | maxq | mb | microblaze | microblazeel | mcore | mep | metag \
...
        | microblaze-* | microblazeel-* \
...
        microblaze*)
                basic_machine=microblaze-xilinx
...

(From OE-Core rev: c052b0c984b28d64527a66ea8e2936ca28b9406f)

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
Signed-off-by: Mark Hatle &lt;mark.hatle@kernel.crashing.org&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemu.inc: add vfat to MACHINE_FEATURES</title>
<updated>2020-01-21T12:52:53+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2020-01-20T17:25:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a21421a96273657de9bdc1e36d5812dc222e6972'/>
<id>urn:sha1:a21421a96273657de9bdc1e36d5812dc222e6972</id>
<content type='text'>
This is beneficial for parted ptests in particular as they
make use of vfat, and fail otherwise.

(From OE-Core rev: ffbc6dc213abf96b816fc9dd87766c3a36935c2a)

Signed-off-by: Alexander Kanavin &lt;alex.kanavin@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
