linux/poky.git/meta/conf/machine/include, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

tunes/arm: add support for newer arm64 cores

2025-10-06T22:15:59+00:00

Add tunes for cores that have been present since GCC 14.1.0. These have been present in meta-arm since mid-July, and have all been verified with fvp-base and testimage. Of those present in meta-arm, arch-armv8-9a.inc, arch-armv9-4a.inc, and arch-armv9-5a.inc have been excluded from this commit, as there are currently issues compiling some packages (but still present in meta-arm for those that want to use them despite those issues). (From OE-Core rev: 6a447745cc247a3570f02dec9db6fa4b6dc03367) Signed-off-by: Jon Mason Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

qemuriscv: Use RVA23S64 profile for cpu

2025-09-25T10:09:05+00:00

Enables RVV extensions uniformly across gcc and clang as it is mandatory in RVA23 spec. https://github.com/riscv/riscv-profiles/blob/main/src/rva23-profile.adoc (From OE-Core rev: 119d63b2e277ca98af593a3fd8add31ca34361af) Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

Revert "qemux86-64: Reduce tuning to core2-64"

2025-08-18T20:14:07+00:00

This was originally applied as our autobuilder had older hardware and couldn't cope with the newer settings. This has been resolved in the new cluster so we can go back to the newer tuning, which software is now more likely to need. This reverts commit 369b1dfa28b1791d45f068acc765190defecd460. (From OE-Core rev: c9585bb8689b6089ce3870910b2dbdb7e9aa547a) Signed-off-by: Richard Purdie

tune-cortexa53: Add nocrypto tune variant

2025-08-14T09:31:10+00:00

crypto is optional on armv8a and Broadcom BCM2837 SoC found on rpi3 does not have hardware acceleration for cryptographic operations. (From OE-Core rev: ef0a34580e71b28a27dcf75285c727fc55c240fc) Signed-off-by: Khem Raj Cc: Jon Mason Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

tune-cortexa72: Add nocrypto tune variant

2025-08-14T09:31:10+00:00

crypto is optional on cortexa72 and some SOCs e.g. BCM2711 (RPI4-fame) do take that option to exclude it. (From OE-Core rev: 3d0de63d07f27e6ce5d58b34c95f90282422c3e6) Signed-off-by: Khem Raj Cc: Jon Mason Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

arm: add nocrypto TUNE_FEATURE to complement crypto

2025-08-14T09:31:10+00:00

Add a `nocrypto` TUNE_FEATURE option to `feature-arm-crypto.inc` to explicitly disable ARM crypto extensions via GCC flags. This provides an opposing state to the existing `crypto` feature, enabling more explicit control over crypto-related tuning. Some vendors ship cores without crypto support, and this change allows disabling it without requiring extensive audits of dependent code paths. This approach avoids the knock-on effects caused when `nocrypto` is applied implicitly in the absence of `crypto` in TUNE_FEATURES. TUNECONFLICTS was added to prevent both features from being enabled simultaneously. When both are added, the following error is seen during build: Feature 'nocrypto' conflicts with 'crypto'. Feature 'crypto' conflicts with 'nocrypto'. (From OE-Core rev: 51e0da4db61abcc546af216609f172204ddb17ab) Signed-off-by: Jon Mason Cc: Ryan Eatmon Cc: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

Revert "feature-arm-crypto: Add +nocrypto to -mcpu when crypto not in features"

2025-08-14T09:31:10+00:00

This reverts commit db1b355b2b15ba57bd89c2dfb88c2c667551863e. (From OE-Core rev: 91615ef0cb1cc1bd20affe03cd98219a9385cb48) Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

bitbake/conf: Default to zstd compressed image output

2025-08-06T21:32:42+00:00

Switch our default qemu images to use .zst compressed images by default since this is the output format we release during the release process and is the one that users would prefer to download. This makes the release process use the actual generated output from the system and avoids post processing. (From OE-Core rev: aa5f60d1fcb716a2b2174dffcaf35442bff1f1fb) Signed-off-by: Richard Purdie

feature-arm-crypto: Add +nocrypto to -mcpu when crypto not in features

2025-08-04T17:04:03+00:00

When crypto is not in tune features then add +nocryto to -mcpu explicitly. This makes the behavior between clang and gcc match. Currently -mcpu=cortex-a72 has different behavior in clang and gcc in terms of what features are considered default. Clang enables different set of common features than gcc on other hand. For example clang enables crypto with default set but gcc does not, gcc recommends to disable unavailable extensions in -mcpu [1] explicitly. crypto is optional on cortex-a53 and cortex-a72. This is not as common but Broadcom SOCs in raspberrypi3/4 have dropped crypto for cost reasons [2]. This results in illegal instruction traps [3] [4] when building components e.g. chromium, qtwebengine, weston etc. with clang using -mcpu=cortex-a72 for rpi4 target. Adding +nocrypto makes clang behave like gcc does today. We do have separate tune if crypto enabled cortex-a72 cores are to be targeted (cortexa72-cryto) as DEFAULTTUNE They are added to default feature file since crypto extension is available in multiple arm architecture versions e.g. armv8, armv9. It is optional extension as per spec [5] Extensions can be enabled and disabled with -mcpu using the same syntax as with -march, and have same effect thats why it is intrumented via TUNE_CCARGS_MARCH_OPTS [1] https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html#index-mcpu-2 [2] https://forums.raspberrypi.com/viewtopic.php?f=63&t=207888#p1332960 [3] https://github.com/llvm/llvm-project/issues/85699 [4] https://github.com/llvm/llvm-project/issues/90365 [5] https://developer.arm.com/documentation/109697/2025_06/Feature-descriptions/The-Armv9-0-architecture-extension (From OE-Core rev: db1b355b2b15ba57bd89c2dfb88c2c667551863e) Signed-off-by: Khem Raj Cc: Quentin Schulz Acked-by: Quentin Schulz Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie