commit | fea636a8486e20e8ccd865670f56d34c9700a043 | [log] [tgz] |
---|---|---|
author | Manojkiran Eda <manojkiran.eda@gmail.com> | Thu Sep 03 16:04:21 2020 +0530 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Tue Oct 06 20:42:03 2020 +0000 |
tree | 3c1aa1cb29623df9befd38170c103fafa33b48c1 | |
parent | 03ff1fa3f6ce475760535c08dfea9b751aa71f65 [diff] |
meta-ibm : switch bmcweb to meson build system - This commit would switch the bmcweb options to meson Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I0e7faf0826f8171cc5c23dd217348213e2a630c7
This layer provides support for the BMC firmware on IBM POWER systems server products.
This layer depends on: URI: git://git.openembedded.org/openembedded-core layers: meta branch: master revision: HEAD URI: https://github.com/openbmc/meta-phosphor branch: master revision: HEAD URI: https://github.com/openbmc/meta-openpower branch: master revision: HEAD URI: https://github.com/openbmc/meta-aspeed branch: master revision: HEAD
The following systems are supported.
Witherspoon, or AC922, is an IBM POWER9 two-socket, 2U Accelerated Compute Server with up to 6 NVIDIA Tesla GPUs. More information can be found here.
In addition to witherspoon, this layer contains additional machine configurations such as swift. The default machine target is witherspoon, so in order to build a different configuration, or to build witherspoon after building a different one, set the MACHINE environment to the desired configuration name (see the conf/machine/ subdirectory for available options):
export MACHINE=machine_configuration_name
Then build:
bitbake obmc-phosphor-image
Example:
export MACHINE=swift bitbake obmc-phosphor-image bitbake phosphor-logging export MACHINE=witherspoon bitbake obmc-phosphor-image
meta-ibm patches are reviewed using the Gerrit instance at https://gerrit.openbmc-project.xyz.
Please submit patches to Gerrit. More information on using Gerrit can be found here. https://github.com/openbmc/meta-ibm is a hosting mirror only and GitHub pull requests are not monitored and will not be accepted.
Patch checklist. Please ensure patches adhere to the following guidelines:
For questions or help please come join us on the mailing list or in IRC.