commit | d3ef5cbeb4b88badde6b954b2f28b718e3ea2f1f | [log] [tgz] |
---|---|---|
author | Matt Spinler <spinler@us.ibm.com> | Thu Dec 14 10:51:56 2017 -0600 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Sat Dec 23 02:42:02 2017 +0000 |
tree | 58bbb339e538e685a6b6003862041f82e569c183 | |
parent | 7b4d8ed1745b53cd58aa34b54b14d641f4930d36 [diff] |
Change wspoon GPU overtemp polling to 500ms For the Witherspoon system, reduce the polling interval for the GPU overtemp condition detected by the UCD90160 power sequencer from 1s to 500ms. This is done to improve fault isolation, as well as HW safety, as the the GPU will turn itself off after 1s of an overtemp so the code may detect a PGOOD fault instead if it doesn't catch it in time. The GPU spec also says to shut off all power on an overtemp as soon as possible to prevent HW damage caused by other connected GPUs still trying to talk to the faulted one. This change will shorten that time, as a hard power off is already issued after an overtemp is detected. Resolves openbmc/openbmc#2719 Change-Id: I1146abfd38e75ec9e9c9fd4f83fe3a9b68c0bd89 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, Open-Embedded, Systemd and DBus 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-openpower/[company]/[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 a 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