MIRRORS/meta-freescale
1
0
Fork 0
mirror of git://git.yoctoproject.org/meta-freescale.git synced 2025-07-19 12:59:04 +02:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
7,681 Commits 26 Branches 2 Tags 57 MiB
BitBake 66.2%
PHP 13.2%
C++ 10.1%
HTML 4.9%
Shell 2.3%
Other 3.3%
0ee7c736c7
Go to file
Jonathan GUILLOT 0ee7c736c7 imx-imx-boot-bootpart.wks.in: Set fixed size for /boot partition 
Using --size in the imx-imx-boot-bootpart.wks.in to set size of /boot
partition does not result in a 256MiB partition as expected but in a
~332MiB one.  Indeed, --size ensures --extra-space (default 10MiB) is
added to actual data size and furthermore applies --overhead-factor
(default 1.3) to the wanted size. This is exactly the case here as 256
* 1.3 = 332.8.

Use --fixed-size instead to force the /boot partition to be exactly
256MiB just as it is indicated in the comments of this file.
Consequently, the `do_image_wic` task will also fail if data copied in
this partition are too large at creation.

Signed-off-by: Jonathan GUILLOT <jonathan@joggee.fr>
2025-02-12 17:10:20 +01:00
.github/workflows Add workflow to automatically update LICENSE file with recipe licenses 2024-12-05 10:32:47 -03:00
classes use-imx-security-controller-firmware: Add i.MX 91 configuration 2025-01-29 08:27:34 +01:00
conf Set default UBOOT_ENTRYPOINT for mx93-generic-bsp 2025-01-30 21:32:56 +01:00
custom-licenses Freescale-EULA: Drop old, unused license 2023-09-06 13:32:26 -07:00
dynamic-layers glmark: Simplify logic for DRM config 2025-01-09 09:06:14 -08:00
recipes-bsp imx-secure-enclave: Bump to lf-6.6.52_2.2.0 2025-02-11 14:09:41 -03:00
recipes-connectivity/iproute2 openssl-qoriq: remove bbappend and patches 2021-10-21 23:54:40 +08:00
recipes-core udev-rules-imx: Use 'install -D' 2024-07-09 16:17:37 -03:00
recipes-devtools qoriq-cst: Update to latest from NXP 6.6.52-2.2.0 2025-01-13 13:58:59 +08:00
recipes-downgrade Upgrade BSP to LF6.6.36_2.1.0 2024-10-25 13:48:21 +03:00
recipes-dpaa fm-ucode: Update license file to LICENSE 2023-07-01 17:17:04 +08:00
recipes-dpaa2 dce: Update to latest from NXP 6.6.52-2.2.0 2025-01-13 13:58:59 +08:00
recipes-extended jailhouse-imx: Update to L6.6.52-2.2.0 release 2025-01-14 06:19:03 +01:00
recipes-fsl packagegroup-fsl-isp: drop the basler-camera-dev package 2025-01-25 13:46:05 +01:00
recipes-graphics imx-gpu-viv: Add missing PROVIDES virtual/libgles3 2025-02-05 07:50:26 -08:00
recipes-kernel linux-fslc: Add changelog link 2025-02-10 22:51:12 +01:00
recipes-multimedia libimxvpuapi2: Upgrade to version 2.3.1 2025-02-07 21:13:15 +01:00
recipes-sato/webkit webkitgtk: Remove x11 from packageconfigs 2023-07-08 15:03:33 -07:00
recipes-security optee-os: add i.mx95 configuration 2024-10-22 00:13:56 +02:00
recipes-support/opencv opencv: Adapt recipe to changes in unpack directories introduced with styhead 2024-10-09 12:20:35 +02:00
SCR SCR: Update to NXP BSP LF6.6.3-1.0.0 2024-04-01 21:48:10 +03:00
scripts scripts: avoid pointless LICENSE churn 2025-01-29 09:40:23 +01:00
wic imx-imx-boot-bootpart.wks.in: Set fixed size for /boot partition 2025-02-12 17:10:20 +01:00
.gitignore .gitignore: add more patterns 2020-04-11 15:34:12 -03:00
COPYING.MIT license: clarify the licensing for the project's metadata 2019-01-10 10:59:06 -02:00
EULA EULA: Update to v57 2024-10-21 18:14:45 +02:00
LICENSE Auto-update LICENSE file with current recipe licenses 2025-02-10 12:39:11 +01:00
README.md Update README with enhanced information and communication channels 2024-04-10 14:59:54 -03:00

README.md

OpenEmbedded/Yocto Project BSP Layer for NXP's Platforms

Welcome to meta-freescale. This document outlines our commitment to providing consistent support and updates in alignment with the Yocto Project LTS release schedule.

This layer provides support for NXP's platforms for use with OpenEmbedded and/or Yocto Project.

Dependencies

This layer depends on:

  • URI: git://git.openembedded.org/openembedded-core
  • Branch: master
  • Revision: HEAD

Branches

  • master: This is our primary development branch, receiving continuous bug fixes and BSP upgrades. It represents the latest and greatest version, ensuring compatibility with the most recent Yocto Project release.
  • scarthgap: Associated with Yocto Project 5.0 (LTS), maintained until April 2028 for bug fixes and until April 2026 for BSP backports.
  • nanbield: Corresponding to Yocto Project 4.3, it's maintained until May 2024 for bug fixes and BSP backports.
  • kirkstone: Tied to Yocto Project 4.0 (LTS), supported until April 2026 for bug fixes and until April 2024 for BSP backports.

Maintenance Policy

  • Latest and Greatest (Master): Continuous attention to bug fixes and BSP upgrades, ensuring that our users have access to the latest enhancements and improvements.
  • Stable Releases: Each stable release is maintained until the subsequent version is released. This includes backports for BSP and critical bug fixes, along with updates for security vulnerabilities (CVEs).
  • Long-Term Support (LTS) Releases: These are maintained for the duration of Yocto Project's LTS support. We prioritize bug fixes, security vulnerabilities (CVEs) updates, and BSP backports to ensure stability and reliability.

This policy ensures that our users can rely on consistent support and updates, backed by our commitment to delivering high-quality BSP layers.

Release Cycle

  • Yocto Project LTS Releases: Our LTS branches follow the Yocto Project LTS release schedule, which involves a four-year maintenance period. A new LTS version is typically released every two years.
  • Stable Releases: We aim to provide stable releases every six months, aligning with the pace of Yocto Project's stable releases.

Contributing

Please submit any patches against the meta-freescale layer by using the GitHub pull-request feature. Fork the repo, create a branch, do the work, rebase from upstream, and then create the pull request.

For useful guidelines on submitting patches, please refer to the Commit Patch Message Guidelines.

Pull requests will be discussed within the GitHub pull-request infrastructure. If you want to stay informed about new PRs and follow-up discussions, please use GitHub's notification system. Additionally, feel free to open GitHub issues for bug reports, feature requests, or general discussions.

Communication