Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / 5fa1bb7bf7949f76214c8b31f4b14a56a68a1f22
commit5fa1bb7bf7949f76214c8b31f4b14a56a68a1f22[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Fri Jun 16 16:22:35 2017 +0930
committerPatrick Williams <patrick@stwcx.xyz>Mon Jun 19 13:59:09 2017 +0000
tree437d9e31a51df6738594fed8e9f949dd823731ca
parent521a5949f2f2d6bb35543193e76ec270abdbeb62 [diff]
kernel: FSI, hwmon, LED GPIO and device tree fixes

Andrew Jeffery (2):
      hwmon: max31785: Clean up uninitialised values
      hwmon: max31785: Use standard sysfs ABI for fast rotor inputs

Cédric Le Goater (5):
      leds: pca955x: add device tree support
      leds: pca955x: use devm_led_classdev_register
      leds: pca955x: add GPIO support
      dt-bindings leds: add pca955x
      ARM: dts: aspeed: witherspoon: Add pca9552 device

Edward A. James (7):
      fsi: occ: Fix 1 byte response and rc for O_NONBLOCK
      hwmon: occ: Add new sensor versions and non-hwmon attributes
      hwmon: occ: Add P8 OCC access
      occ: hwmon and fsi probing fix
      ARM: aspeed: Power9 dts and defconfigs for OCC
      drivers: fsi: sbefifo: Fix buffer initialization
      drivers: hwmon: occ: Add "master" attribute and remove status files

Joel Stanley (1):
      ARM: configs: aspeed: Add pca9552 driver

Rick Altherr (1):
      ARM: dts: aspeed: quanta-q71l: Add i2c and LED devices

Change-Id: I9d1307cd3d8e0eaa86197a2da858dd0d83174d6c
Signed-off-by: Joel Stanley <joel@jms.id.au>
3 files changed
tree: 437d9e31a51df6738594fed8e9f949dd823731ca
  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.

Finding out more

Dive deeper in to OpenBMC by opening the docs repository

Contact