MIRRORS/meta-freescale
1
0
Fork 0
mirror of git://git.yoctoproject.org/meta-freescale.git synced 2025-10-22 14:52:19 +02:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
7,219 Commits 20 Branches 2 Tags 58 MiB
BitBake 67.5%
PHP 12.1%
C++ 10.3%
HTML 4.8%
Shell 2.3%
Other 3%
73bd34eaf6
Go to file
Otavio Salvador 73bd34eaf6 Update README with enhanced information and communication channels 
Enhanced the README file by adding detailed maintenance policies for the
`meta-freescale` layer, including information about branch management
and release cycles.

Additionally, included specifics about the maintained branches such as
`master`, `scarthgap`, `nanbield`, and `kirkstone`. This update aims to
provide users with a clearer understanding of the project's maintenance
practices and available branches.

Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2024-04-10 14:59:54 -03:00
.github/workflows cicd: backport: Fix events allowing the workflow to run 2021-08-09 10:15:38 -03:00
classes uuu_bootloader_tag.bbclass: Use UUU_BOOTLOADER_TAGGED variable 2024-03-09 19:14:32 -03:00
conf conf/layer: add bmaptool compatibility for old versions 2024-03-11 12:02:36 +00:00
custom-licenses Freescale-EULA: Drop old, unused license 2023-09-06 13:32:26 -07:00
dynamic-layers qtbase: Enable wayland knob when in distro features 2024-03-02 10:12:48 -08:00
recipes-bsp u-boot-imx_2023.04.bb: Add UUU_BOOTLOADER_UNTAGGED variable 2024-03-09 09:48:30 -03:00
recipes-connectivity/iproute2 openssl-qoriq: remove bbappend and patches 2021-10-21 23:54:40 +08:00
recipes-core ls2080ardb: drop as it is unbuildable for too long 2023-10-12 20:27:43 -03:00
recipes-devtools uuu: add libtinyxml2 to the build dependencies 2024-02-17 16:01:06 +01:00
recipes-downgrade spir: Downgrade to 1.3.239.0.imx 2023-10-31 12:00:08 -07:00
recipes-dpaa fm-ucode: Update license file to LICENSE 2023-07-01 17:17:04 +08:00
recipes-dpaa2 dce_git.bb: Set SRCREV_FORMAT variable as multiple SCMs are used 2023-10-21 22:35:39 +08:00
recipes-extended jailhouse-imx: Update the recipe to align to the NXP BSP LF6.1.55_2.2.0 2024-02-07 17:12:42 -03:00
recipes-fsl mcore-demos: README: Update the information 2024-01-25 14:03:38 -03:00
recipes-graphics Merge pull request #1747 from thochstein/imx-gpu-viv 2024-02-08 10:29:31 -03:00
recipes-kernel Merge pull request #1723 from valijec/master 2024-02-05 16:20:24 -03:00
recipes-multimedia recipes-multimedia: Update for NXP release 6.1.55-2.2.0 2024-02-12 12:06:51 +02:00
recipes-sato/webkit webkitgtk: Remove x11 from packageconfigs 2023-07-08 15:03:33 -07:00
recipes-security optee-test: Upgrade to lf-6.1.55-2.2.0 (4.0) 2024-02-17 11:40:44 +02:00
recipes-support/opencv opencv: Integrate 225ce6a14a to fix build protobuf v22 and dnn enabled 2023-10-12 14:39:57 +02:00
SCR EULA,SCR: Update for NXP release 6.1.36-2.1.0 2023-10-30 14:29:11 -07:00
scripts Ensure we fail if old SoC overrides are in use 2022-03-03 10:41:35 -03:00
wic imx-uboot-mxs-bootpart.wks.in: drop extra 'rootfs' 2023-11-12 12:23:55 -05: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,SCR: Update to v49 for NXP release 6.1.55-2.2.0 2024-01-16 10:34:29 +01:00
LICENSE license: clarify the licensing for the project's metadata 2019-01-10 10:59:06 -02: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