commit | 25c9a63084a97790d62d2bbb9db3cd64b91db5d4 | [log] [tgz] |
---|---|---|
author | Matt Spinler <spinler@us.ibm.com> | Fri Mar 09 10:54:09 2018 -0600 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Wed Mar 14 15:16:44 2018 -0400 |
tree | 4fa9066ef39a89cb538f4a853fca1dd2e3bbcd5a | |
parent | d683d87130f7a3aad1e3fc8382a98b94fb81b16b [diff] |
Use OpenPower variable for PS derating factor The openpower-occ-control code needs to know the power supply derating factor, but will default to a value if one isn't supplied externally in do_configure. Since other will also need to use that same value, use a common variable for it defined in openpower.inc, and now pass it into the configure step. This derating factor is an OpenPower concept used by the Power processor's OCC thermal control subsystem. Tested: Check that the derating factor variable in config.h in the openenpower-occ-control repo follows the variable in openpower.inc. Change-Id: I259b6086ebe70b2ac6eccdd244e43a7d36a28a77 Signed-off-by: Matt Spinler <spinler@us.ibm.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 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. 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
Machine | TEMPLATECONF |
---|---|
Palmetto | meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf |
Barreleye | meta-openbmc-machines/meta-openpower/meta-rackspace/meta-barreleye/conf |
Zaius | meta-openbmc-machines/meta-openpower/meta-ingrasys/meta-zaius/conf |
Witherspoon | meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/conf |
As an example target Palmetto
export TEMPLATECONF=meta-openbmc-machines/meta-openpower/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 in to OpenBMC by opening the docs repository.