linux/meta-freescale.git/conf/machine/include, branch master

imx-base: Move the i.MX SDK host tools to TOOLCHAIN_HOST_TASK

2026-08-07T12:30:01+00:00

A bbappend to nativesdk-packagegroup-sdk-host added nativesdk-imx-usb-loader, nativesdk-mxsldr, nativesdk-u-boot-mkimage and nativesdk-wayland to RDEPENDS unconditionally, so an SDK built for any machine in a build with meta-freescale in BBLAYERS picked up i.MX flashing tools. Measured on qemuarm64 with bitbake -e: RDEPENDS gained exactly those four. The obvious fix -- scoping that RDEPENDS to a machine override -- would be worse than the leak. That packagegroup has a fixed PACKAGE_ARCH of ${SDK_ARCH}-nativesdk, so making its contents depend on MACHINE would emit different package content under one package architecture, and two SDKs built from the same TMPDIR would overwrite each other in the feed. oe-core's own recipe is careful here: it varies only by SDK_ARCH and DISTRO_FEATURES, never by MACHINE. Drop the bbappend and add the tools to TOOLCHAIN_HOST_TASK in imx-base.inc instead. populate_sdk_base consumes that variable in the SDK recipe, which is already machine-specific, so there is no package-architecture hazard. imx-base.inc is required only by i.MX machine configurations -- 27 of them, no QorIQ -- and the append is additionally scoped to imx-generic-bsp to match the IMAGE_CLASSES line above it. Measured with bitbake -e, before vs after: qemuarm64 TOOLCHAIN_HOST_TASK gains none of the four tools imx6qdlsabresd TOOLCHAIN_HOST_TASK gains exactly the four tools; nothing else in the expansion moves Note for QorIQ: those machines previously received these tools through the unconditional bbappend and no longer do. Three of the four are i.MX-specific, so this is intended, but it is a behaviour change for machines this layer does own. bitbake -p: 1166 recipes, 0 errors. No SDK was built, so the effect on a populated SDK is inferred from TOOLCHAIN_HOST_TASK, not measured. Signed-off-by: Luciano Dittgen

imx-base.inc: Set IMX_BOOTLOADER_PTABLE to gpt for i.MX 8/9 only

2026-07-31T21:45:04+00:00

Even variable IMX_BOOTLOADER_PTABLE is used in imx-imx-boot-bootpart.wks.in only, add thus SoC specific setting to avoid confusing. Signed-off-by: Jun Zhu

imx-base.inc: remove duplicated firmware installation

2026-07-31T05:33:14+00:00

Every SoC has their corresponding firmwares listed with *-generic-bsp. There is no need to install imx6 VPU firmware on all i.MX mainline BSPs. Remove the duplicate entry. Signed-off-by: Alexander Stein

gst/gstreamer: Bump 1.26.6 -> 1.28.1

2026-07-27T07:29:55+00:00

Update license file reference: COPYING -> LICENSE.txt gstreamer1.0-vaapi remains at 1.26.6 Signed-off-by: Flora Hu

imx-imx-boot-bootpart.wks.in: Use variable to choose ptable type

2026-07-22T03:46:39+00:00

In NXP i.MX BSP, i.MX 8 & 9 is preferred to use gpt ptable: - Boot ROM Compatibility: i.MX 8/9 Boot ROM can work with both MBR and GPT - U-Boot Configuration: NXP U-Boot has configured to recognize GPT (CONFIG_EFI_PARTITION=y) - Partition Alignment: GPT first usable LBA in GPT is in sector 34 (17KB), and i.MX 8&9 has IMX_BOOT_SEEK offset (32-33KB), so no conflict - Advantages of GPT - Support for >2TB storage (not typically relevant for SD cards) - More robust with CRC32 checksums and backup partition table - Up to 128 partitions vs 4 primary partitions in MBR - Better partition naming and GUID identification Signed-off-by: Jun Zhu

opencv: sync 4.13.0.imx recipe with meta-imx and fix build

2026-07-16T20:06:07+00:00

The recipe was imported with style adjustments from opencv_4.6.0.imx.bb that diverged from the meta-imx 4.13.0 source, breaking the i.MX build: - Restore the -DCPU_DISPATCH=SSE,... form (the -DENABLE_SSE=1 flags and the EXTRA_OECMAKE:remove:x86 workaround were leftovers from 4.6.0). - Pass KLEIDICV_SOURCE_PATH on aarch64 so configure uses the pre-fetched Kleidicv source instead of attempting a network download. - Keep the /usr/bin/cpp rename, which OpenCV 4.13 still installs. Select 4.13.0.imx for the mx8 and mx9 NXP BSP overrides. Signed-off-by: Luciano Dittgen

imx-base.inc: set SECOEXT_FIRMWARE_NAME to empty by default

2026-04-28T08:34:11+00:00

SECOEXT_FIRMWARE_NAME is set to 'UNDEFINED' by default. Since commit d7930c6e ("firmware-ele-imx: Bump 2.0.2 -> 2.0.5"), the firmware-ele-imx recipe fails during do_install if this variable is not overridden. The install step tries to access a non-existent path named 'UNDEFINED', resulting in: install: cannot stat '.../UNDEFINED': No such file or directory Set SECOEXT_FIRMWARE_NAME to an empty value to prevent build failures when the parameter is not explicitly defined. Signed-off-by: Benjamin Missey

Merge pull request #2488 from nxp-upstream/BSP-upgrade-to-6.18.2

2026-04-27T16:05:02+00:00

Bsp: upgrade to 6.18.2

Merge pull request #2490 from nxp-upstream/weston-libdrm-update

2026-04-27T16:04:16+00:00

Weston/libdrm update to lf-6.18.2

conf/machine: Drop non-existent image type sdcard

2026-04-27T12:11:20+00:00

This is a follow-up to commit 777cb1b05ba7 ("conf/machine: Drop non-existent image type sdcard") Original commit message: The machine configuration files specify an image type `sdcard` via `UBOOT_CONFIG`. This type is not listed in `IMAGE_TYPES`, and the specification appears to have no effect on the build. It appears to be historical only and of no use, so drop it. Signed-off-by: Christophe Guerreiro