Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 83a4307ecef9a5451af4f46ca3f84c1b45d9cd1b
commit83a4307ecef9a5451af4f46ca3f84c1b45d9cd1b[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Fri Aug 11 17:06:50 2017 +0930
committerPatrick Williams <patrick@stwcx.xyz>Tue Aug 15 04:42:38 2017 +0000
tree92d58831e97fc72706ae291b1e3842cee30d46bd
parentd9300f647562af92520cb1915d3d0a472df72afc [diff]
kernel: IBM PSU driver, hwmon core additions, and aspeed-pwm-tacho

Edward A. James (8):
      hwmon: (pmbus): Switch status registers to 16 bit
      hwmon: (pmbus): Access word data for STATUS_WORD
      hwmon: (pmbus): Add generic alarm bit for iin and pin
      hwmon: (pmbus): Add debugfs for status registers
      dt-bindings: i2c: Document the IBM CCF power supply version 1
      hwmon: (pmbus): Add IBM Common Form Factor (CFF) power supply driver
      Documentation: hwmon: Document the IBM CFF power supply
      ARM: dts: aspeed: Witherspoon: Add power supplies to i2c bus

Jaghathiswari Rankappagounder Natarajan (1):
      Documentation: dt-bindings: Document bindings for ASPEED AST2400/AST2500 PWM and Fan tach control

Joel Stanley (2):
      ARM: configs: aspeed: Add VLAN options
      ARM: configs: aspeed: Enable IBM CFF Power Supply driver

Mykola Kostenok (2):
      Documentation: dt-bindings: aspeed-pwm-tacho cooling device.
      hwmon: (aspeed-pwm-tacho) cooling device support.

Change-Id: I78081bba5af67a1b1987fe256dd1f2ff3182472d
Signed-off-by: Joel Stanley <joel@jms.id.au>
3 files changed
tree: 92d58831e97fc72706ae291b1e3842cee30d46bd
  1. import-layers/
  2. meta-openbmc-bsp/
  3. meta-openbmc-machines/
  4. meta-phosphor/
  5. bitbake ⇨ import-layers/yocto-poky/bitbake
  6. documentation ⇨ import-layers/yocto-poky/documentation
  7. LICENSE ⇨ import-layers/yocto-poky/LICENSE
  8. meta ⇨ import-layers/yocto-poky/meta
  9. meta-poky ⇨ import-layers/yocto-poky/meta-poky
  10. meta-selftest ⇨ import-layers/yocto-poky/meta-selftest
  11. meta-skeleton ⇨ import-layers/yocto-poky/meta-skeleton
  12. meta-yocto-bsp ⇨ import-layers/yocto-poky/meta-yocto-bsp
  13. oe-init-build-env ⇨ import-layers/yocto-poky/oe-init-build-env
  14. oe-init-build-env-memres ⇨ import-layers/yocto-poky/oe-init-build-env-memres
  15. scripts ⇨ import-layers/yocto-poky/scripts
  16. .gitignore
  17. .gitreview
  18. .templateconf
  19. openbmc-env
  20. README.md
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, Open-Embedded, Systemd and DBus 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 23
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake
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. 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

MachineTEMPLATECONF
Palmettometa-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf
Barreleyemeta-openbmc-machines/meta-openpower/meta-rackspace/meta-barreleye/conf
Zaiusmeta-openbmc-machines/meta-openpower/meta-ingrasys/meta-zaius/conf
Witherspoonmeta-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

3) 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 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.

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

  • REST Management
  • IPMI
  • SSH based SOL
  • Power and Cooling Management
  • Event Logs
  • Zeroconf discoverable
  • Sensors
  • Inventory
  • LED Management
  • Host Watchdog
  • Simulation

Features In Progress

  • Code Update Support for multiple BMC/BIOS images
  • POWER On Chip Controller (OCC) Support
  • Full IPMI 2.0 Compliance with DCMI
  • Verified Boot
  • HTML5 Java Script Web User Interface
  • BMC RAS

Features Requested but need help

  • OpenCompute Redfish Compliance
  • OpenBMC performance monitoring
  • cgroup user management and policies
  • Remote KVM
  • Remote USB
  • OpenStack Ironic Integration
  • QEMU enhancements

Finding out more

Dive deeper in to OpenBMC by opening the docs repository

Contact