commit | 331ddf251ce94e6d14f354b44565545bb95c1ed7 | [log] [tgz] |
---|---|---|
author | Andrew Jeffery <andrew@aj.id.au> | Mon Apr 08 16:51:30 2019 +0930 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Mon Apr 15 23:00:48 2019 -0400 |
tree | 033e260325910eaa3a31df85137656115b5ee4f3 | |
parent | d95f139c007f21d5d8395d0bd7a6e0bab0fd6124 [diff] |
mboxd: Depend on xyz.openbmc_project.Control.Host This is one of the bus names claimed by ipmid, and according to bea22141ca95 ("Ensure ipmid doesn't start until on dbus") it's the last to be claimed. Depend on this to ensure our required IPMI services are available. I've observed a reasonably reliable difference in behaviour between depending on the canonical service (phosphor-ipmi-host.service) vs the alias (xyz.openbmc_project.Control.Host.service) in that setAttention()s from mboxd state changes were propagated as expected in the latter case but not in the former. (From meta-phosphor rev: 3b0c37e3e0bf2a6f6e9cca7f4f1e49f4c79cc1e1) Change-Id: Ibcda190e28aa169923f80f48ab98a2a2bd890e4a Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
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 rpcgen sudo dnf groupinstall "C Development Tools and Libraries"
git clone git@github.com:openbmc/openbmc.git cd openbmc
Any build requires an environment variable known as TEMPLATECONF
to be set to a hardware target. You can see all of the known targets with find meta-* -name local.conf.sample
. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet
Machine | TEMPLATECONF |
---|---|
Palmetto | meta-ibm/meta-palmetto/conf |
Zaius | meta-ingrasys/meta-zaius/conf |
Witherspoon | meta-ibm/meta-witherspoon/conf |
Romulus | meta-ibm/meta-romulus/conf |
As an example target Palmetto
export TEMPLATECONF=meta-ibm/meta-palmetto/conf
. 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.
Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.
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.
Feature List
Features In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.