|author||Patrick Williams <firstname.lastname@example.org>||Thu Jan 20 11:06:23 2022 -0600|
|committer||Patrick Williams <email@example.com>||Thu Jan 20 11:06:26 2022 -0600|
meta-security: subtree update:a85fbe980e..c20b35b527 Anton Antonov (1): Parsec service. Update PACKAGECONFIG definitions and README.md Armin Kuster (20): python3-fail2ban: fix build failure and cleanup meta-parsec/README: remove rust layer req. opendnssec: blacklist do to ldns being blacklisted apparmor: Add a python 3.10 compatability patch tpm2-tools: update to 5.2 openssl-tpm-engine: fix build issue with openssl 3 tpm2-openssl: add new pkg tpm2-pkcs11: update to 1.7.0 recipes: Update SRC_URI branch and protocols sssd: Create /var/log/sssd in runtime bastille: Create /var/log/Bastille in runtime python3-fail2ban: remove /run tpm2-pkcs11: update to 1.7.0 libest: does not build with openssl 3.x clamav: fix useradd warning python3-fail2ban: update to tip tpm2-pkcs11: backport openssl 3.x build fixes packagegroup-security-tpm2: drop ibmswtpm2 meta-integrity: drop strongswan bbappends meta-tpm: drop strongswan bbappends Kai Kang (2): sssd: re-package to fix QA issues apparmor: fix warning of remove operator combined with += Kristian Klausen (2): swtpm: update to 0.6.1 dm-verity-img.bbclass: Fix wrong override syntax for CONVERSION_DEPENDS Liwei Song (1): recipes-security/chipsec: platform security assessment framework Stefan Mueller-Klieser (1): tpm2-tss: fix fapi package config Yi Zhao (2): openssl-tpm-engine: fix warning for append operator combined with += meta-parsec/README.md: fix for append operator combined with += Signed-off-by: Patrick Williams <firstname.lastname@example.org> Change-Id: I2156e47cf3f4f45daa2b60a73e3b46be3b6a86c0
OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your platform.
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake \ rpcgen perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum sudo dnf groupinstall "C Development Tools and Libraries"
git clone email@example.com:openbmc/openbmc.git cd openbmc
Any build requires an environment set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called
setup and takes the name of your hardware target as an argument.
The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:
$ . setup <machine> [build_dir] Target machine must be specified. Use one of: bletchley gsj romulus dl360poc kudo s2600wf e3c246d4i mihawk swift ethanolx mtjade tiogapass evb-ast2500 nicole transformers evb-ast2600 olympus-nuvoton witherspoon evb-npcm750 on5263m5 witherspoon-tacoma f0b p10bmc x11spi fp5280g2 palmetto yosemitev2 g220a qemuarm zaius gbs quanta-q71l
Once you know the target (e.g. romulus), source the
setup script as follows:
. setup romulus
Additional details can be found in the docs repository.
The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here
Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile
make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.
Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.
Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
First, please do a search on the internet. There's a good chance your question has already been asked.
For technical discussions, please see contact info below for Discord and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or Discord.
Features In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.
The Technical Steering Committee (TSC) guides the project. Members are: