commit | 94055d98af7050623300d79dd865dfcec6bf0d5f | [log] [tgz] |
---|---|---|
author | Andrew Geissler <openbmcbump-github@yahoo.com> | Tue Aug 06 15:11:18 2019 +0000 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Tue Aug 06 14:03:43 2019 -0400 |
tree | 4f3f803ca54acb7947d11ff44b902f6d02e2669f | |
parent | bdd5f541e8ef8d92f12d2a964fc9c95709d42944 [diff] |
phosphor-logging: srcrev bump 0a2c1a2332..3fb83b3787 Matt Spinler (15): Add libstdc++fs to test_ldflags Makefile var PEL: Add class to wrap AdditionalData PEL: Add PEL Manager class PEL: Add Stream class to manipulate PEL data PEL: Add BCD time helpers for PELs PEL: Add PEL section header structure PEL: Add PrivateHeader class PEL: Add UserHeader class PEL: Add function to generate unique PEL IDs PEL: Add PEL class PEL: Add repository to save PELs PEL: Remove a PEL based on an ID PEL: New repository method to get PEL data Factor out log creation code common code. Implement Logging.Create interface (From meta-phosphor rev: d5d70cf023e723b6a0f9cd79679048546efc8a1f) Change-Id: Ic031986092bf8bfe36a8484769f0f3becebbc8b2 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.