|author||Andrew Geissler <email@example.com>||Mon Oct 25 18:50:41 2021 +0000|
|committer||Andrew Geissler <firstname.lastname@example.org>||Wed Oct 27 01:40:17 2021 +0000|
pyphosphor: srcrev bump d2aadf1220..cb240aa1ed Manojkiran Eda (1): Add OWNERS file Change-Id: I7894d02007f281ab04735db611af0faf3853bb7a Signed-off-by: Andrew Geissler <email@example.com>
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 firstname.lastname@example.org: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 hr630 quanta-q71l centriq2400-rep hr855xg2 romulus dl360poc kudo s2600wf e3c246d4i lanyang stardragon4800-rep2 ethanolx mihawk swift evb-ast2500 mtjade thor evb-ast2600 neptune tiogapass evb-npcm750 nicole transformers evb-zx3-pm3 olympus witherspoon f0b olympus-nuvoton witherspoon-tacoma fp5280g2 on5263m5 x11spi g220a p10bmc yosemitev2 gbs palmetto zaius gsj qemuarm
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: