|author||Lei YU <firstname.lastname@example.org>||Fri May 24 13:44:01 2019 +0800|
|committer||Brad Bishop <email@example.com>||Tue May 28 18:36:52 2019 -0400|
meta-romulus: Set RemainAfterExit for phosphor-cooling-type service The service phosphor-cooling-type is required by multi-user.target and thus will be started by default. In case multi-user.target is started for multiple times, this service will be startd for multiple times as well, and eventually get start-limit-hit failure. This commit adds RemainAfterExit=true so the service will be treated as started and thus will not be started for multiple times. Resolves openbmc/openbmc#3544 Tested: Reboot Romulus BMC when the host is on, and verify the BMC gets READY state after reboot. (From meta-ibm rev: fdd8f7bb1cca6b505d6b92c741d04a9c6bbfafa7) Change-Id: Ie3817296265c860d770333c59b591da9d083139c Signed-off-by: Lei YU <firstname.lastname@example.org> Signed-off-by: Brad Bishop <email@example.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 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 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
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 into OpenBMC by opening the docs repository.