meta-openembedded: subtree update:ce51958eca..a2928764c2

Adrian Bunk (3):
      python3-cmd2: Remove PNBLACKLIST
      php: Remove no longer needed CFLAGS_append_aarch64
      php: Move more into after php5 removal

Alistair Francis (4):
      python3-requests-future: Initial commit of 0.9.5
      python3-xmlrunner: Initial commit of 1.7.7
      python3-fasteners: Initial commit of 0.15
      python3-python-vlc: Initial commit of 3.0.7110

Anuj Mittal (3):
      python3-defusedxml: add recipe
      python-networkx: upgrade 2.1 -> 2.2
      python3-networkx: add recipe

Khem Raj (9):
      php: Turn PCRE JIT off for riscv
      redis: Fix build with clang/x86
      android-tools: Recognise i686 for HOST_ARCH
      netdata: Update to 1.17.0 and fix build with clang/x86
      safec: Define _GNU_SOURCE
      safec: Upgrade to 3.5 release
      openocd: Add --disable-werror always
      breakpad: Update dont-clobber-rsp patch to latest
      gparted: add to deps instead of overwriting

Martin Jansa (3):
      remmina: add distro_features_check for GTK3DISTROFEATURES
      ceres-solver: fix the paths in .cmake files
      ceres-solver: add PACKAGECONFIG for suitesparse and lapack

Naveen Saini (1):
      pm-graph: upgrade 5.3 -> 5.5

Oleksandr Kravchuk (1):
      analyze-suspend: update to 5.5

Peter Kjellerstedt (1):
      lvm2/libdevmapper: Make it build for native

Randy MacLeod (1):
      poppler: update from 0.79.0 to 0.80.0

Slater, Joseph (1):
      openhpi: control snmp-bc ptest generation

Stefan Agner (1):
      fuse3: add libfuse3 recipe

Trevor Gamblin (1):
      gvfs: upgrade 1.40.2 -> 1.41.2 for CVE fixes

Yi Zhao (2):
      php: fix module path in mod_php.conf
      apache-websocket: fix module path

Yuan Chao (2):
      python-atomicwrites: new recipe
      python-pytest: fix runtime error

Zang Ruochen (1):
      python-certifi: upgrade 2019.6.16 -> 2019.9.11

Change-Id: Iba065b25686a1ac22d647226d9ea0c61c5b4578f
Signed-off-by: Brad Bishop <>
43 files changed
tree: 675a1c6f76065884b0c99b5a6056c79de44ef083
  1. .github/
  2. meta-arm/
  3. meta-aspeed/
  4. meta-evb/
  5. meta-facebook/
  6. meta-google/
  7. meta-hxt/
  8. meta-ibm/
  9. meta-ingrasys/
  10. meta-inspur/
  11. meta-intel/
  12. meta-inventec/
  13. meta-lenovo/
  14. meta-mellanox/
  15. meta-microsoft/
  16. meta-nuvoton/
  17. meta-openembedded/
  18. meta-openpower/
  19. meta-phosphor/
  20. meta-portwell/
  21. meta-qualcomm/
  22. meta-quanta/
  23. meta-raspberrypi/
  24. meta-security/
  25. meta-x86/
  26. meta-xilinx/
  27. meta-yadro/
  28. poky/
  29. .gitignore
  30. .gitreview
  31. .templateconf
  33. openbmc-env
  35. setup


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, OpenEmbedded, systemd, and D-Bus 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 28
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake \
    rpcgen perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum
sudo dnf groupinstall "C Development Tools and Libraries"

2) Download the source

git clone
cd openbmc

3) Target your hardware

Any build requires an environment variable known as TEMPLATECONF to be set to a hardware target. You can see all of the known targets with find meta-* -name local.conf.sample. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet


As an example target Palmetto

export TEMPLATECONF=meta-ibm/meta-palmetto/conf

4) 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 an 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.

Features of OpenBMC

Feature List

  • Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
  • Full IPMI 2.0 Compliance with DCMI
  • Code Update Support for multiple BMC/BIOS images
  • Web-based user interface
  • REST interfaces
  • D-Bus based interfaces
  • SSH based SOL
  • Remote KVM
  • Hardware Simulation
  • Automated Testing

Features In Progress

  • OpenCompute Redfish Compliance
  • User management
  • Virtual media
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.