Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / 2d058c05ec81e57f0b7d2e61e5f48d2425d11c22
commit2d058c05ec81e57f0b7d2e61e5f48d2425d11c22[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Fri Feb 03 12:00:16 2017 +1030
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Thu Feb 09 01:54:11 2017 +0000
tree66ac74419e8e0a0323b2ed5b00c273ded2ce3217
parent4458d4939a33672bf3fc5113523c6d2453478371 [diff]
kernel: Add FSP FSI I2C driver and Zaius UART fix

This bumps the kernel to include a port of the FSI I2C driver from the
FSP. It drives the I2C master in the CFAM logic of the host processor
over FSI. This driver is being rewritten to be a proper i2c bus driver,
and as such will be removed once that driver is functionally equivalent.

There is also a fix for the Zaius UART.

A device tree for the Qanta Q71L, a non-openpower BMC, was added.

Christopher Bostic (3):
  drivers/fsi: Add slave interrupt polling
  drivers/fsi: Add Client IRQ Enable / Disable
  drivers/fsi: Add sysfs file to adjust i-poll period

Edward A. James (5):
  drivers: fsi: Add i2c client driver
  drivers: fsi: i2c: Add engine access wrappers
  drivers: fsi: i2c: probe fsi device for i2c client
  drivers: fsi: i2c: add driver file operations and bus locking
  drivers: fsi: i2c: boe engine

Joel Stanley (2):
  drivers: fsi: Fix compilation warnings
  aspeed: defconfig: add FSI_I2C driver

Rick Altherr via openbmc (2):
  dts: Minimal device tree for Quanta Q71L BMC
  arm: aspeed: zaius: Disable LPC reset for UART1

Change-Id: I4fd4e4e347cfe3dead1d84de8b79dc2121346b02
Signed-off-by: Joel Stanley <joel@jms.id.au>
3 files changed
tree: 66ac74419e8e0a0323b2ed5b00c273ded2ce3217
  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] (https://github.com/openbmc/docs/blob/master/cheatsheet.md)

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] (http://robotframework.org/) 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