Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / 999ce88a6d235b4fad994b7668e0902ae274057a
commit999ce88a6d235b4fad994b7668e0902ae274057a[log] [tgz]
authorMatthew Barth <msbarth@us.ibm.com>Fri May 31 16:37:16 2019 -0500
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Wed Jun 05 09:34:12 2019 -0400
treedc2fa6d4b5085ec8e05b3935238545372dbc17ee
parent466193732b3fe99986982f5ca444fb221d0b970d [diff]
swift: Add CP1 ir35219 and ir35221 sensors

On processor 1 in Swift, an IR35219 is used for the VDD vrm and
IR35221s are used for the VDN & VCS vrms and VIO vrm. Initially the
same warn/crit configuration values as Witherspoon will be used.

Tested:
    Built image that contained the config files

(From meta-ibm rev: a296aa3c0ad4278c060c66c4ca4c1ed5913cfe06)

Change-Id: I961c12469c550d36ec03bc5f249fe46019d1c5d1
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
4 files changed
tree: dc2fa6d4b5085ec8e05b3935238545372dbc17ee
  1. .github/
  2. meta-arm/
  3. meta-aspeed/
  4. meta-evb/
  5. meta-facebook/
  6. meta-google/
  7. meta-hxt/
  8. meta-ibm/
  9. meta-ingrasys/
  10. meta-inspur/
  11. meta-intel/
  12. meta-inventec/
  13. meta-lenovo/
  14. meta-mellanox/
  15. meta-nuvoton/
  16. meta-openembedded/
  17. meta-openpower/
  18. meta-phosphor/
  19. meta-portwell/
  20. meta-qualcomm/
  21. meta-quanta/
  22. meta-raspberrypi/
  23. meta-security/
  24. meta-x86/
  25. meta-xilinx/
  26. poky/
  27. bitbake ⇨ poky/bitbake/
  28. LICENSE ⇨ poky/LICENSE
  29. meta ⇨ poky/meta
  30. meta-poky ⇨ poky/meta-poky/
  31. meta-skeleton ⇨ poky/meta-skeleton
  32. oe-init-build-env ⇨ poky/oe-init-build-env
  33. scripts ⇨ poky/scripts/
  34. .gitignore
  35. .gitreview
  36. .templateconf
  37. MAINTAINERS
  38. openbmc-env
  39. README.md
  40. setup
README.md

OpenBMC

Build Status

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.

Setting up your OpenBMC project

1) Prerequisite

  • Ubuntu 14.04
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
  • Fedora 28
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"

2) Download the source

git clone git@github.com:openbmc/openbmc.git
cd openbmc

3) Target your hardware

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

MachineTEMPLATECONF
Palmettometa-ibm/meta-palmetto/conf
Zaiusmeta-ingrasys/meta-zaius/conf
Witherspoonmeta-ibm/meta-witherspoon/conf
Romulusmeta-ibm/meta-romulus/conf

As an example target Palmetto

export TEMPLATECONF=meta-ibm/meta-palmetto/conf

4) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

Build Validation and Testing

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.

Submitting Patches

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.

Bug Reporting

Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.

Features of OpenBMC

Feature List

  • Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
  • Full IPMI 2.0 Compliance with DCMI
  • Code Update Support for multiple BMC/BIOS images
  • Web-based user interface
  • REST interfaces
  • D-Bus based interfaces
  • SSH based SOL
  • Remote KVM
  • Hardware Simulation
  • Automated Testing

Features In Progress

  • OpenCompute Redfish Compliance
  • User management
  • Virtual media
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Contact