meta-openembedded: subtree update:3a9262866d..55de2d06ad

Adrian Bunk (1):
      python-more-itertools: Add PE

Andreas Müller (1):
      Add gnome help packages to image according to IMAGE_LINGUAS

Andreas Oberritter (2):
      live555: Move test progams out of main package
      pugixml: Update to version 1.10

André Draszik (7):
      gyp: update to fcd686f1880f
      gyp: provide a python2 version of gyp as gyp-py2
      nodejs: ensure to use correct compiler & flags always
      nodejs: delete all bundled deps in do_unpack() if needed
      nodejs: allow use of system gyp
      nodejs: use OE-provided compiler flags (arm)
      nodejs: support long directory names for ${B} / ${S}

Denys Dmytriyenko (1):
      mbedtls: upgrade 2.16.2 -> 2.16.3

Fabio Berton (5):
      python-importlib-metadata: Add native and nativesdk to BBCLASSEXTEND
      python-more-itertools: Add native and nativesdk to BBCLASSEXTEND
      python-pathlib2: Add native and nativesdk to BBCLASSEXTEND
      python-zipp: Add native and nativesdk to BBCLASSEXTEND
      python3-importlib-metadata: RDEPEND python3-misc only for target and nativesdk

Khem Raj (13):
      sip: Upgrade to 4.19.19
      cherokee: Update to latest
      cherokee: Fix build when time_t is 64bit
      tvheadend: Update to tip of master
      lowpan-tools: Blacklist as its deprecated use wpan-tools instead
      pidgin-sipe: Fix build when time_t is 64bit
      open-vm-tools: Enable tirpc explicitly, fix build with 64bit time_t
      python-systemd: Include endian.h for htobe16
      tvheadend: Fix build with 64bit time_t
      tvheadend: Set CLEANBROKEN
      layer.conf: Add ttf-roboto->fontconfig to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS
      layer.conf: Add phpmyadmin->php dep to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS
      python-six: Update to 1.13.0

Michael Scott (1):
      modemmanager: Upgrade 1.10.6 -> 1.10.8

Nicola Lunghi (5):
      python3-gmqtt: add recipe
      python-backports-abc: update to 0.5.0
      python-rfc3339-validator: add recipe
      python-rfc3986-validator: add recipe
      python-dbus-next: fix recipe position

Peace Lee (1):
      guider: upgrade 3.9.4 -> 3.9.6

Trevor Gamblin (4):
      python3-werkzeug: upgrade from 0.14.1 to 0.16.0
      python3-flask: upgrade from 1.0.2 to 1.1.1
      python3-itsdangerous: upgrade from 0.24 to 1.1.0
      zabbix: upgrade 4.2.8 -> 4.4.1

Yi Zhao (1):
      python-ipy: add recipes

Zang Ruochen (15):
      fuse3: upgrade 3.7.0 -> 3.8.0
      python-alembic: upgrade 1.2.1 -> 1.3.0
      python-astroid: upgrade 2.3.2 -> 2.3.3
      python-bitarray: upgrade 1.0.1 -> 1.1.0
      python-cffi: upgrade 1.13.1 -> 1.13.2
      python-dateutil: upgrade 2.8.0 -> 2.8.1
      python-psutil: upgrade 5.6.3 -> 5.6.5
      python-pycryptodome: upgrade 3.9.0 -> 3.9.3
      python-pyparsing: upgrade 2.4.2 -> 2.4.5
      python-pytest-helpers-namespace: upgrade 2016.7.10 -> 2019.1.8
      python-pytest-runner: upgrade 5.1 -> 5.2
      python-pytest-tempdir: upgrade 2016.8.20 -> 2019.10.12
      python-requests-oauthlib: upgrade 0.8.0 -> 1.3.0
      python-tornado: upgrade 5.1 -> 6.0.3
      python-tqdm: upgrade 4.31.1 -> 4.38.0

Zheng Ruoqin (1):
      f2fs-tools: Update Homepage

Change-Id: Ifc2d7bac36a719f2a4ead82b491d9817f212c56f
Signed-off-by: Brad Bishop <>
106 files changed
tree: 2ccd0491dca6659964161e0c3252dc9fb9b1c1e8
  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 Romulus

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

4) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

OpenBMC Development

The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here

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.


First, please do a search on the internet. There's a good chance your question has already been asked.

For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.

For technical discussions, please see contact info below for IRC and mailing list information.

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.