Skip to content

quic-yocto/meta-qcom-hwe

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

53 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

meta-qcom-hwe

merge main

Introduction

OpenEmbedded/Yocto Project hardware enablement layer for Qualcomm based platforms.

This layers provides additional recipes and machine configuration files for Qualcomm platforms.

This layer depends on:

URI: https://github.com/openembedded/openembedded-core.git
layers: meta
branch: master
revision: HEAD

URI: https://github.com/Linaro/meta-qcom.git
branch: master
revision: HEAD

Branches

  • main: Primary development branch, with focus on upstream support and compatibility with the most recent Yocto Project release.
  • kirkstone: Qualcomm Linux 1.x, aligned with Yocto Project 4.0 (LTS).

Machine Support

See conf/machine for the complete list of supported devices.

Quick build

Please refer to the Yocto Project Reference Manual to set up your Yocto Project build environment.

Please follow the instructions below for a KAS-based build. The KAS tool offers an easy way to setup bitbake based projects. For more details, visit the KAS documentation.

  1. Install kas tool
    sudo pip3 install kas
    
  2. Clone meta-qcom-hwe layer
    git clone https://github.com/quic-yocto/meta-qcom-hwe.git -b main
    
  3. Build using the KAS configuration for one of the supported boards
    kas build meta-qcom-hwe/ci/qcs6490-rb3gen2-core-kit.yml
    

For a manual build without KAS, refer to the Yocto Project Quick Build.

Contributing

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

For some useful guidelines when submitting patches, please refer to: https://docs.yoctoproject.org/dev/contributor-guide/submit-changes.html#preparing-changes-for-submission

Pull requests will be discussed within the GitHub pull-request infrastructure.

Branch kirkstone is not open for direct contributions, please raise an issue with the suggested change instead.

Communication

Maintainer(s)

License

This layer is licensed under the MIT license. Check out COPYING.MIT for more detais.