|author||Konstantin Aladyshev <firstname.lastname@example.org>||Thu Apr 22 15:16:12 2021 +0300|
|committer||Konstantin Aladyshev <email@example.com>||Wed Aug 25 08:24:01 2021 +0000|
meta-ethanolx: Add blacklist file for the 'fru-device' app Some I2C addresses can't be probed for a FRU. For example, device at this address can be already connected to a driver or the I2C bus is not scannable like the APML bus. In this case 'fru-device' app will be producing messages like this: 'fru-device[XXX]: device at bus X address XX busy' To avoid these unnecessary log messages add I2C bus blacklist json file for the 'fru-device' app. Signed-off-by: Konstantin Aladyshev <firstname.lastname@example.org> Change-Id: I0618943c9362117d9931defa1e17bcd999621197
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: centriq2400-rep f0b fp5280g2 gsj hr630 hr855xg2 lanyang mihawk msn neptune nicole olympus olympus-nuvoton on5263m5 p10bmc palmetto qemuarm quanta-q71l romulus s2600wf stardragon4800-rep2 swift tiogapass vesnin witherspoon witherspoon-tacoma yosemitev2 zaius
Once you know the target (e.g. romulus), source the
setup script as follows:
. setup romulus
For evb-ast2500, please use the below command to specify the machine config, because the machine in
meta-aspeed layer is in a BSP layer and does not build the openbmc image.
TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env
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: