<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-freescale.git/classes, branch master</title>
<subtitle>Mirror of github.com/Freescale/meta-freescale</subtitle>
<id>https://git.enea.com/cgit/linux/meta-freescale.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-freescale.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/'/>
<updated>2026-10-28T11:38:00+00:00</updated>
<entry>
<title>use-imx-security-controller-firmware: Add i.MX 952 configuration</title>
<updated>2026-10-28T11:38:00+00:00</updated>
<author>
<name>Matheus Barbosa</name>
<email>matheus.barbosa@toradex.com</email>
</author>
<published>2026-10-27T16:44:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=57f7a2a10a5f94a1d28e7ffd25aaaf2ab0d1cb71'/>
<id>urn:sha1:57f7a2a10a5f94a1d28e7ffd25aaaf2ab0d1cb71</id>
<content type='text'>
Add the SECO FW file name for i.MX 952.

Based on LF6.18.37_2.1.0 NXP BSP release.

Signed-off-by: Matheus Barbosa &lt;matheus.barbosa@toradex.com&gt;
</content>
</entry>
<entry>
<title>EULA: Update to v64.2</title>
<updated>2026-10-19T16:58:15+00:00</updated>
<author>
<name>Rodrigo M. Duarte</name>
<email>rodrigo.duarte@ossystems.com.br</email>
</author>
<published>2026-10-19T16:58:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=3e8cfe47974d9a43cf45caad6a68ee81893504fa'/>
<id>urn:sha1:3e8cfe47974d9a43cf45caad6a68ee81893504fa</id>
<content type='text'>
This version is used in NXP release 6.18.37-2.1.0. Compared to v63, it
updates the version line and adds the terms for software components
provided by Vector Informatik GmbH.

Add the v64.2 checksum to FSL_EULA_FILE_MD5SUMS so packages shipping
the new license are accepted, and use it as the layer EULA checksum.
Packages still shipping v63 keep working, as their checksum remains in
the list.

Tested with 'bitbake firmware-imx -c populate_lic' (MACHINE=imx8mq-evk):
the layer EULA is found with the v64.2 checksum and the v63 package
EULA of firmware-imx 8.32 is still accepted.

Signed-off-by: Rodrigo M. Duarte &lt;rodrigo.duarte@ossystems.com.br&gt;
</content>
</entry>
<entry>
<title>Merge pull request #2827 from rprasanth/qoriq-features-check-warning</title>
<updated>2026-10-16T01:15:05+00:00</updated>
<author>
<name>Otavio Salvador</name>
<email>otavio@ossystems.com.br</email>
</author>
<published>2026-10-16T01:15:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=30898f119b51038a2ba37ae3e03e2030051f91bc'/>
<id>urn:sha1:30898f119b51038a2ba37ae3e03e2030051f91bc</id>
<content type='text'>
qoriq_build_64bit_kernel: Avoid unused features_check warning</content>
</entry>
<entry>
<title>qoriq_build_64bit_kernel: Avoid unused features_check warning</title>
<updated>2026-10-16T00:02:33+00:00</updated>
<author>
<name>Prasanth R</name>
<email>ragaprasanth@gmail.com</email>
</author>
<published>2026-10-15T07:44:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=98d3ab34cc24faf47dc1217a9a09db7514b9f035'/>
<id>urn:sha1:98d3ab34cc24faf47dc1217a9a09db7514b9f035</id>
<content type='text'>
REQUIRED_DISTRO_FEATURES is only appended for e6500 now, so on any
other machine features_check sees it unset and warns for lttng-modules:

"Recipe inherits features_check but doesn't use it"

Fixes: 838e986 ("qoriq_build_64bit_kernel: Append the multiarch distro feature")

Signed-off-by: Prasanth R &lt;prasanth.r@lineo.co.jp&gt;
</content>
</entry>
<entry>
<title>Merge pull request #2822 from lucianogdittgen/fsl-dynamic-packagearch-sstate-archs</title>
<updated>2026-10-15T18:15:41+00:00</updated>
<author>
<name>Otavio Salvador</name>
<email>otavio@ossystems.com.br</email>
</author>
<published>2026-10-15T18:15:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=463b6bba3d250be773ce3adf1ff422a057953f09'/>
<id>urn:sha1:463b6bba3d250be773ce3adf1ff422a057953f09</id>
<content type='text'>
fsl-dynamic-packagearch: Add the SoC architectures to SSTATE_ARCHS</content>
</entry>
<entry>
<title>fsl-dynamic-packagearch: Share the SoC architecture list</title>
<updated>2026-10-15T12:14:48+00:00</updated>
<author>
<name>Otavio Salvador</name>
<email>otavio@ossystems.com.br</email>
</author>
<published>2026-10-15T12:14:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=b066c37416acb14c016fec83baf4c540c7a4ee99'/>
<id>urn:sha1:b066c37416acb14c016fec83baf4c540c7a4ee99</id>
<content type='text'>
The anonymous function and fsl_dynamic_packagearch_sstate_archs() each
built the list of SoC architectures, so a change to one could leave
SSTATE_ARCHS out of step with PACKAGE_EXTRA_ARCHS.

Move the list into fsl_dynamic_packagearch_extra_archs(): the anonymous
function appends its result to PACKAGE_EXTRA_ARCHS, as before, and
fsl_dynamic_packagearch_sstate_archs() adds the ones not yet in
PACKAGE_ARCHS to SSTATE_ARCHS.

PACKAGE_EXTRA_ARCHS, PACKAGE_ARCHS and SSTATE_ARCHS are unchanged, in
the configuration and for busybox (with ARM_INSTRUCTION_SET "arm") and
libdrm, on imx6qdlsabresd, imx8mp-lpddr4-evk, imx8mn-lpddr4-evk,
t2080rdb and ls1046ardb, and with a lib32 multilib on imx8mp-lpddr4-evk.

Signed-off-by: Otavio Salvador &lt;otavio@ossystems.com.br&gt;
</content>
</entry>
<entry>
<title>Merge pull request #2798 from lucianogdittgen/check-layer-socarch-wayland-protocols</title>
<updated>2026-10-14T13:24:02+00:00</updated>
<author>
<name>Otavio Salvador</name>
<email>otavio@ossystems.com.br</email>
</author>
<published>2026-10-14T13:24:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=054e5836686c4a30eb33f48631d9b71ca2ae6db1'/>
<id>urn:sha1:054e5836686c4a30eb33f48631d9b71ca2ae6db1</id>
<content type='text'>
wayland-protocols: Move the i.MX protocols to wayland-protocols-imx</content>
</entry>
<entry>
<title>wayland-protocols: Move the i.MX protocols to wayland-protocols-imx</title>
<updated>2026-10-14T12:27:19+00:00</updated>
<author>
<name>Luciano Dittgen</name>
<email>luciano.dittgen@ossystems.com.br</email>
</author>
<published>2026-10-05T18:36:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=5398fdd691c14fcd22f839d07230e5beaf4c7551'/>
<id>urn:sha1:5398fdd691c14fcd22f839d07230e5beaf4c7551</id>
<content type='text'>
The bbappend patched wayland-protocols on every NXP BSP machine and
built it per SoC, so every recipe built against it (libxkbcommon,
systemd, dbus, glib-2.0 and about 80 more on one tune) differed between
SoCs and from the mainline BSP machines, which fails yocto-check-layer
test_machine_signatures.

Only the i.MX weston and gstreamer1.0-plugins-bad use the NXP protocols:
both call the add_dtrc_meta request added to zwp_linux_buffer_params_v1,
and weston 10.0.5.imx, the default on mx6 and mx7, also implements the
alpha-compositing and hdr10-metadata protocols.

Follow the model of linux-imx-headers and use-imx-headers:

- wayland-protocols-imx installs a copy of the staged wayland-protocols
  tree, carrying the three patches, in ${datadir}/imx/wayland-protocols,
  with its own wayland-protocols.pc in ${datadir}/imx/pkgconfig. It is
  named after the wayland-protocols version it copies, is NXP BSP only,
  and is SoC arch through MACHINE_SOCARCH_FILTER, so the recipes
  depending on it are SoC arch too.
- use-imx-wayland-protocols makes a recipe depend on it on the NXP BSP,
  points meson's pkg_config_path to it so
  dependency('wayland-protocols') finds the i.MX copy, and propagates it
  to the SDK through ${PN}-dev.

The i.MX weston and gstreamer1.0-plugins-bad inherit the class, and
wayland-protocols stays stock and allarch for everything else.

The patches are regenerated from the NXP fork, branch
wayland-protocols-imx-1.41, and the alpha-compositing and hdr10-metadata
ones are trimmed to their protocol XML, as they apply to the installed
tree, not the source. The hdr10-metadata XML keeps the fork's CRLF line
endings.

Signed-off-by: Luciano Dittgen &lt;luciano.dittgen@ossystems.com.br&gt;
</content>
</entry>
<entry>
<title>fsl-dynamic-packagearch: Add the SoC architectures to SSTATE_ARCHS</title>
<updated>2026-10-14T12:27:00+00:00</updated>
<author>
<name>Luciano Dittgen</name>
<email>luciano.dittgen@ossystems.com.br</email>
</author>
<published>2026-10-13T20:20:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=33263562d129055ff93c5eed6b9d53fc53783a90'/>
<id>urn:sha1:33263562d129055ff93c5eed6b9d53fc53783a90</id>
<content type='text'>
The class adds the SoC architectures to PACKAGE_EXTRA_ARCHS from an
anonymous function, so only within a recipe: the configuration's
SSTATE_ARCHS does not list them.

OE-core prunes, after parsing, the sysroot manifests of recipes no
longer built for an architecture, but only for the architectures in
the configuration's SSTATE_ARCHS. A recipe leaving a SoC architecture
in an existing build directory therefore keeps its old manifest, and
the recipe sysroots of SoC architecture recipes, which search the SoC
architecture before allarch and the tune ones, still take the old
output. For example, after wayland-protocols moves from the SoC
architecture to allarch, recipes keep getting the old patched copy.

Add the SoC architectures, including the ARM/Thumb and multilib ones
the anonymous function adds, to SSTATE_ARCHS. Within a recipe they are
already in PACKAGE_EXTRA_ARCHS, so nothing is added there.

Signed-off-by: Luciano Dittgen &lt;luciano.dittgen@ossystems.com.br&gt;
</content>
</entry>
<entry>
<title>qoriq_build_64bit_kernel: Build the e6500 kernel with the biarch compiler</title>
<updated>2026-10-07T11:53:13+00:00</updated>
<author>
<name>Luciano Dittgen</name>
<email>luciano.dittgen@ossystems.com.br</email>
</author>
<published>2026-10-06T18:25:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=4c974fa192aeea41c1eacf280866bdb6f6f8ab66'/>
<id>urn:sha1:4c974fa192aeea41c1eacf280866bdb6f6f8ab66</id>
<content type='text'>
The lib64 multilib in e6500.inc existed only to give the 64-bit kernel a
compiler, but multiarch (already required) makes gcc-cross-powerpc biarch.
Dropping it ends the signature split it caused (yocto-check-layer
test_machine_signatures) and restores kernel-arch's prefix-map flags.
Tested: buildhistory pair of linux-qoriq on t2080rdb; .text is identical
instruction by instruction, only addresses move with .rodata.

Signed-off-by: Luciano Dittgen &lt;luciano.dittgen@ossystems.com.br&gt;
</content>
</entry>
</feed>
