commit | bde651bb18ca73fd6240ae0400f016c76c547a45 | [log] [tgz] |
---|---|---|
author | Matt Spinler <spinler@us.ibm.com> | Tue May 16 10:49:57 2017 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Mon May 22 23:13:35 2017 +0000 |
tree | 58d425f78224e742cc39854fd3d86533169f5573 | |
parent | 6a3b4bef5ebb5e32d0bdca2405eb56ea9056c9c2 [diff] |
Make use of obmc-fan-control-ready@.target This involves the following: * Start the fan-control-init@.service on a power on. * That service will set fans to full speed, delay for a bit, and then start the obmc-fan-control-ready target. * This target will start the fan monitor and real fan control services. * On a power off, the target and these services will be deactivated. Doing it this way ensures the fans will have had time to ramp up from a cold start before applications start looking at them. Currently, on a reboot at runtime the same thing will occur. The watchdog would have already brought the fans to high speed, so this will extend that time at full speed by another 20 (or similar, it's configurable) seconds, ensuring we know what speed the fans are at. Resolves openbmc/openbmc#1567 Change-Id: I73a1f91f0efaf319df97b59334073116d45f40c3 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.
Dive deeper in to OpenBMC by opening the docs repository