<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-xilinx.git/conf/machine/include, branch pyro</title>
<subtitle>Mirror of git.yoctoproject.org/meta-xilinx.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-xilinx.git/atom?h=pyro</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-xilinx.git/atom?h=pyro'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/'/>
<updated>2017-11-14T09:13:56+00:00</updated>
<entry>
<title>machine-xilinx-default.inc: Remove image_types_uboot</title>
<updated>2017-11-14T09:13:56+00:00</updated>
<author>
<name>Alistair Francis</name>
<email>alistair.francis@xilinx.com</email>
</author>
<published>2017-08-18T16:29:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=b6462e55e65b44afed4b7a4e8b2af3381c961110'/>
<id>urn:sha1:b6462e55e65b44afed4b7a4e8b2af3381c961110</id>
<content type='text'>
This has changed in the meta layer and breaks the build, as it appears
it is no longer required just remove it.

Signed-off-by: Alistair Francis &lt;alistair.francis@xilinx.com&gt;
Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
</content>
</entry>
<entry>
<title>zynqmp-pmu-config.inc: Limit to specific recipes</title>
<updated>2017-08-27T09:15:41+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2017-08-18T13:28:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=3c5ac860edcb7d26a0cbf01a460e5c63ab50c68d'/>
<id>urn:sha1:3c5ac860edcb7d26a0cbf01a460e5c63ab50c68d</id>
<content type='text'>
Limit the appending/enabling of the zynqmp-pmu BBCLASSEXTEND to only
specific recipes which are used for the building of pmu-firmware. This
is just binutils, gcc, newlib, libgloss and pmu-firmware itself.

The limiting is done based on the BPN of the recipe, which is not
provided as an override so the conditional is tested with an inline
python function.

This change removes the need for the extender class to be enabled
globally which can conflict with certain recipes that were not written
to be extended by the BBCLASSEXTEND mechanism. This change also improves
the parse time avoiding the need to parse all recipes for both target
and zynqmp-pmu.

Add comment for the PACKAGE_EXTRA_ARCHS setting, so it is clear why it
is set.

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
Acked-by: Alistair Francis &lt;alistair.francis@xilinx.com&gt;
Tested-by: Alistair Francis &lt;alistair.francis@xilinx.com&gt;
</content>
</entry>
<entry>
<title>zcu102-zynqmp: Setup the use of multiarch QEMU</title>
<updated>2017-06-03T06:55:31+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2017-05-30T11:30:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=c9b8ff6881cc94cf10b57e3d184cf39125facee6'/>
<id>urn:sha1:c9b8ff6881cc94cf10b57e3d184cf39125facee6</id>
<content type='text'>
Setup the qemuboot variables and qemu-xilinx-helper-native environment
to use the multiarch script to start a QEMU multiarch instance with the
MicroBlaze PMU.

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
Tested-by: Alistair Francis &lt;alistair.francis@xilinx.com&gt;
</content>
</entry>
<entry>
<title>zcu102-zynqmp: Enable building of PMU recipes and build pmu firmware</title>
<updated>2017-06-03T06:55:31+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2017-05-30T11:02:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=b9339b852c4876265d3b194cf29094012ecf2d90'/>
<id>urn:sha1:b9339b852c4876265d3b194cf29094012ecf2d90</id>
<content type='text'>
Enable the building of 'zynqmp-pmu' recipes, and setup the pmu-firmware
to be built for the image.

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
Tested-by: Alistair Francis &lt;alistair.francis@xilinx.com&gt;
Tested-by: Koteswararao Nayudu &lt;kotin@xilinx.com&gt;
</content>
</entry>
<entry>
<title>machine-xilinx-default.inc: Remove xserver-xorg-extension-glx</title>
<updated>2017-05-30T09:35:10+00:00</updated>
<author>
<name>Manjukumar Matha</name>
<email>manjukumar.harthikote-matha@xilinx.com</email>
</author>
<published>2017-05-26T22:02:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=b3a1bb6145ee2291b6f5b35154e032fabad77fb0'/>
<id>urn:sha1:b3a1bb6145ee2291b6f5b35154e032fabad77fb0</id>
<content type='text'>
xserver-xorg-extension-glx is a software support, the performance is not
validate on Xilinx platform. Instead convert application to depend on
egl/gles1/gles2. MALI400 provides the required hardware acceleration

Signed-off-by: Manjukumar Matha &lt;manjukumar.harthikote-matha@xilinx.com&gt;
Reviewed-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
</content>
</entry>
<entry>
<title>zcu102-zynqmp.conf: Remove mali as machine feature</title>
<updated>2017-05-30T09:30:28+00:00</updated>
<author>
<name>Manjukumar Matha</name>
<email>manjukumar.harthikote-matha@xilinx.com</email>
</author>
<published>2017-05-26T22:00:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=d0979730c2ac7951f97ffb02c07ad1ad3e117b32'/>
<id>urn:sha1:d0979730c2ac7951f97ffb02c07ad1ad3e117b32</id>
<content type='text'>
Remove mali as machine feature. This is not required, any dependencies
on mali userspace libraries should be resolved through gles1/gles2/egl
preffered provider. for ex:
PREFERRED_PROVIDER_virtual/libgles1_zynqmp = "libmali-xlnx"
PREFERRED_PROVIDER_virtual/libgles2_zynqmp = "libmali-xlnx"
PREFERRED_PROVIDER_virtual/egl_zynqmp = "libmali-xlnx"

MALI userspace libraries inturn should depends on out-of-tree mali
kernel module.

Signed-off-by: Manjukumar Matha &lt;manjukumar.harthikote-matha@xilinx.com&gt;
Reviewed-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
</content>
</entry>
<entry>
<title>feature-microblaze-versions.inc: Simplify version formatting functions</title>
<updated>2017-05-30T08:46:21+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2017-05-30T08:46:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=c017b2a016429560223a0f8654994bc772977460'/>
<id>urn:sha1:c017b2a016429560223a0f8654994bc772977460</id>
<content type='text'>
Simplify the functions used to generate the TUNE_CCARGS and PKGARCH
version strings.

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
</content>
</entry>
<entry>
<title>arch-microblaze.inc: Invert how the 'reorder' feature is used for v8.30</title>
<updated>2017-05-30T08:46:21+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2017-05-30T08:46:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=c519c5ee2b725e6f946ffd11c862463b3391876e'/>
<id>urn:sha1:c519c5ee2b725e6f946ffd11c862463b3391876e</id>
<content type='text'>
With Xilinx MicroBlaze v8.30 a configuration issue requires that the
'pattern-compare' feature is enable for the 'reorder' feature to be
correctly functional. Previously the MicroBlaze tune setup would assume
that 'pattern-compare' was available even when it may not actually be,
and would force enable the 'pattern-compare' feature automatically. This
behaviour is prone to issues and may emit broken binaries for a target
when the user was not aware or expected that there target CPU was
broken.

This change inverts the behaviour such that instead of implicitly
enabling the 'pattern-compare' feature it instead does not enable
generation of reorder instructions for the compiler by setting
'-mno-xl-reorder' in the same way as the case that the target does not
have the feature enabled.

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
</content>
</entry>
<entry>
<title>machine-xilinx-default.inc: Remove version pinning for linux-xlnx</title>
<updated>2017-05-15T11:27:31+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2017-05-15T11:27:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=eb1497ce130e6ac60dd1200a86b23e6bd19e4fc0'/>
<id>urn:sha1:eb1497ce130e6ac60dd1200a86b23e6bd19e4fc0</id>
<content type='text'>
Remove the version pinning for linux-xlnx, this allows for using the
newest version available without needing to change the include.

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
</content>
</entry>
<entry>
<title>qemuboot-xilinx.bbclass: Rework qemu-xilinx setup</title>
<updated>2017-04-27T14:22:19+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan@nathanrossi.com</email>
</author>
<published>2017-04-13T14:05:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=3119a03a3db979541a5a20884e393c3b0868f9b5'/>
<id>urn:sha1:3119a03a3db979541a5a20884e393c3b0868f9b5</id>
<content type='text'>
This change reworks how the meta-xilinx layer enables and provides the
custom version of QEMU based on Xilinx's fork of QEMU. The existing
implementation relied on the single sysroot which was changed in oe-core
such that now recipes have their own sysroots (RSS support).
Additionally oe-core now provides the QEMU binaries to the runqemu
script via the 'qemu-helper-native' recipes sysroot as opposed to the
image sysroot.

These rework changes allow for a single machine to select the targeted
QEMU version as well as to provide the qemuboot config specific to the
targeted QEMU version. The selection of QEMU version is now handled by
PREFERRED_PROVIDER mechanics with the meta-xilinx layer providing an
additional recipe that is equivalent to qemu-helper-native and which
also provides said target allowing for the machine to select via the use
of PREFERRED_PROVIDER_qemu-helper-native. This recipe
(qemu-xilinx-helper-native) however instead provides the sysroot
populated with qemu-xilinx instead of qemu.

Additionally the XILINX_QEMUBOOT variable is replaced with the
qemuboot-xilinx.bbclass, this provides the overrides for setting up
qemu-xilinx specific QB_* args. Additionally this bbclass points runqemu
at the qemu-xilinx-helper-native sysroot for QEMU binaries.

These changes also work towards making the meta-xilinx layer better
handle multiple qemuboot.conf variants as well as handling different
QEMU versions.

This change also removes the 'qemu-system-xilinx' MACHINE_FEATURES, this
is due to MACHINE_FEATURES no longer being available for native recipes.
Additionally there is no longer any logic that needs to know this any
way.

Signed-off-by: Nathan Rossi &lt;nathan@nathanrossi.com&gt;
Reviewed-by: Alistair Francis &lt;alistair.francis@xilinx.com&gt;
</content>
</entry>
</feed>
