commit | 350321028176d2e1d209209521a9dd7f8f4551f8 | [log] [tgz] |
---|---|---|
author | Andrew Geissler <openbmcbump-github@yahoo.com> | Mon Jul 01 20:40:58 2019 +0000 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Mon Jul 08 22:23:39 2019 -0400 |
tree | 4014ecdc614d593f83b86fe7bd1899a4a3a1e49e | |
parent | f16037c36b9243a735cdc1345ebbc9287d7dec45 [diff] |
intel-ipmi-oem: srcrev bump 60e7aaf5c0..606dd9f763 Chen,Yugang (1): Static code analysis scan issue fix James Feist (1): Add support to set LED for ME Events Jason M. Bills (6): Update Get SM Signal command for front panel buttons Update MessageId to match the registry Add Set Front Panel Button Enables command Update AC fail check to new DBus parameter Add Get System Restart Cause command Fix privilege level for storage commands Vernon Mauery (4): convert appcommands.cpp to unix line endings update exception paths in MDRv2 handlers replace sdbusplus::message::variant_ns with std remove legacy ipmid_get_sd_bus_connection calls (From meta-intel rev: 4e2b239447fa61d9cbafbe7b231ff2651761fe26) Change-Id: Ie3c01421ff300c16a47dfc04fd74947928d3fb91 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com> 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 perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum 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.