Page History

...

• Version upgrades for bitbake , GStreamer, and other OE components
• Linux kernel 5.4 or above
• Extensible SDK

...

For platform-specific recipes, keep them in the SoC meta-layer. While it is a good practice to start afresh with a new manifest for the target platform, a manifest file for a similar featured platform can be used as a starting point too. Check all device-specific repos in the reference manifest, and ensure corresponding device repos are created for this new device as needed, and update the manifest with these updated repos

• Create artifactory repo for the project with appropriate permissions for vendors. This is used for hosting any binaries required for the project
• Check-in SoC components - toolchain, SDK, kernel, drivers, etc.. to corresponding SoC Gerrit repos/ artifactory as applicable
• Populate meta SoC layer with the initial set of changes needed to build a kernel, SoC components, etc..
• If there is any SoC reference board exists, create a corresponding machine configuration in the SoC layer, and create an image target to be able to build a final image for the reference board. This layer should be separated out within the meta SoC layer from other common SoC, common chip sub-layers which will be usually used by the meta OEM layer as well.
• Populate meta OEM layer with machine configuration and other bare minimum changes required to generate a target image for OEM board.
• Machine configuration can be updated with the "NEEDED_BSPLAYERS" field to include required SoC, OEM layers in the build
• Any unwanted recipes during the early stage of bringing up can be masked using BBMASK if needed.

...