Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / 69f645f20f5e7cd55f8e621570a596f6c7b5a340
commit69f645f20f5e7cd55f8e621570a596f6c7b5a340[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Fri Feb 24 16:26:46 2017 +1030
committerPatrick Williams <patrick@stwcx.xyz>Fri Feb 24 16:10:09 2017 +0000
tree22c1c5c1fe3df429f65d81064d36779daf779815
parente84a33bc2be987a3cebd283e0d01668f2b4de59d [diff]
kernel: Enable UBI, FSI hub support and device tree updates

This introduces hub master support for the FSI driver, enabling it to initialise
and talk to the FSI address space on the second socket of P9 machines.

UBI and UBIFS support is enabled in the kernel in preparation for using them in
OpenBMC.

The P9 device trees have been brought in sync with each other, with all now
describing the mailbox and lpc drivers necessary for using mboxd for host boot
firmware communication.

Adriana Kobylak (1):
  arm: configs: aspeed: Add UBI support

Christopher Bostic (4):
  drivers/fsi: Add hub master support
  drivers/fsi: Move common read/write code into shared utility
  drivers/fsi: Cleanup and retry op on error
  drivers/fsi: Initialize slave link field

Edward A. James (3):
  drivers: fsi: scom: Zero out user buffer first
  drivers: fsi: Fix FSI core size checking user interfaces
  drivers: fsi: i2c: Fixup probe to allow multiple engines

Joel Stanley (2):
  ARM: dts: aspeed: Fix RAM size in Romulus and Witherspoon
  ARM: dts: aspeed: Reserve RAM on P9 machines

Lei YU (1):
  ARM: dts: aspeed: Enable Romulus mailbox and LPC control nodes

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