Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / 00e2ea8259190768d071fae98534acd412890061
commit00e2ea8259190768d071fae98534acd412890061[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Mon Feb 13 12:40:08 2017 +1030
committerPatrick Williams <patrick@stwcx.xyz>Mon Feb 20 13:13:36 2017 +0000
tree665055bca050ab2be0e83ae7beee1a1fa5eefe8a
parentb792af2f796950107d273b68f0fde673164028a2 [diff]
kernel: FSI fixes and GPIO pinmux loopback patch

A bunch of fixes to FSI and the legacy FSP I2C driver, as well as adding FSI
bindings to Witherspoon and Zaius. Neither platform has enabled the driver at
this stage as we require pdbg to move to the kernel API.

Christopher Bostic (2):
  fsi: Adjust slave ID based on address
  drivers/fsi: Clock slave prior to master command

Edward A. James (6):
  drivers: fsi: i2c fix probing
  drivers: fsi: Enable missing i2c ports
  drivers: fsi: Delete device on unscan
  drivers: fsi: scom: Add remove function
  drivers: fsi: Fix incremeting dev nums
  drivers: fsi: i2c: Change fsi irq enable behavior

Joel Stanley (4):
  fsi: i2c: Silence warnings
  ARM: dts: aspeed: Add FSI pins to Zaius device tree
  Revert "drivers: fsi: Fix incremeting dev nums"
  Revert "drivers/fsi: Clock slave prior to master command"

Rick Altherr (1):
  aspeed: pinctrl: Allow disabling Port D and Port E loopback mode

Change-Id: Ibbb9d63a3a6f64b0fb89c3c54840447ba689a5e5
Signed-off-by: Joel Stanley <joel@jms.id.au>
1 file changed
tree: 665055bca050ab2be0e83ae7beee1a1fa5eefe8a
  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