|Benjamin Fair <firstname.lastname@example.org>
|Wed Jun 20 14:57:10 2018 -0700
|Brad Bishop <email@example.com>
|Mon Jul 16 03:53:34 2018 +0000
npcm7xx: kernel: replace linux-obmc with linux-nuvoton The linux-obmc recipe has been removed and BSPs are expected to provide their own Linux recipes now. This updates the Nuvoton BSP to include its own Linux recipe so it can build successfully again. Change-Id: I61e0cf0745be6ae4e282b32abf36aad4c5f4b860 Signed-off-by: Benjamin Fair <firstname.lastname@example.org>
The OpenBMC project can be described as a Linux distribution for embedded devices that have a BMC; typically, but not limited to, things like servers, top of rack switches or RAID appliances. The OpenBMC stack uses technologies such as Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your server 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 sudo dnf groupinstall "C Development Tools and Libraries"
git clone email@example.com:openbmc/openbmc.git cd openbmc
Any build requires an environment variable known as
TEMPLATECONF to be set to a hardware target. OpenBMC has placed all known hardware targets in a standard directory structure
meta-openbmc-machines/meta-[architecture]/meta-[company]/meta-[target]. You can see all of the known targets with
find meta-openbmc-machines -type d -name conf. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet
As an example target Palmetto
. openbmc-env bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
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.
Features In Progress
Features Requested but need help
Dive deeper in to OpenBMC by opening the docs repository.