|author||Andrei Kartashev <firstname.lastname@example.org>||Thu Dec 09 12:47:47 2021 +0300|
|committer||Andrei Kartashev <email@example.com>||Tue Dec 14 13:39:17 2021 +0000|
obmc-yadro-lsinventory: srcrev bump d0bdf0ddd1..d8e25f82ff Alexander Filippov (3): Add remote host support use any inventory managers replace json-c with nlohmann/json Signed-off-by: Andrei Kartashev <firstname.lastname@example.org> Change-Id: I7b7b9214c909e6b0d147d17339c73c203e78fcb3
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: