Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 2c567ba2d10ed18eda0eddef933a3be0b7ecf166
commit2c567ba2d10ed18eda0eddef933a3be0b7ecf166[log] [tgz]
authorAndrew Jeffery <andrew@aj.id.au>Tue Apr 18 16:30:10 2017 +0930
committerPatrick Williams <patrick@stwcx.xyz>Wed Apr 19 18:40:10 2017 +0000
tree241544bc39f6c30be9a76c07e627569eff37eb47
parentb6e965c04f41e07113855dce737dccd9dfdb4282 [diff]
mboxd: Bump version and use mboxctl to reset the daemon

The updated mboxd and associated mboxctl fix the need to sleep when
resetting the mbox daemon state, and implement v2 of the mbox protocol.

mboxd now defaults to using 1MiB windows filling the reserved space if
no relevant options are specified on the commandline. The systemd unit
file explicitly specifies 1MiB for clarity, but leaves the number of
windows unspecified to allow flexibility in the size of the reserved
memory. Currently the devicetree reserves 64MiB, but this is likely to
be reduced to 16MiB in the near future. A 1MiB window size currently
covers all but three partitions on the PNOR, and experiments with a 2MiB
window size didn't show any drastic improvements over 1MiB in boot times.

The changes have been tested on a Witherspoon system using the
reboot-loop scripts developed when debugging the UCD90160/I2C issue.
mboxd survived all 30-40 reboots; some issues were encountered, though
they all appeared to be unrelated failures in Hostboot's DDR procedures.

Fixes openbmc/openbmc#1045.

Change-Id: Ia0343a3c3195d526a6d97bb1d056b62bc6088711
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
3 files changed
tree: 241544bc39f6c30be9a76c07e627569eff37eb47
  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