meta-openembedded: subtree update:53d431639a..e4ac09169d

Andreas Müller (9):
      file-roller: add gsettings to inherit
      tracker: add gsettings to inherit
      nautilus: add gsettings to inherit
      libgweather: add gsetings & upstream-version-is-even to inherit
      gnome-settings-daemon: add gsettings to inherit
      gnome-terminal: add gsettings to inherit
      parole: upgrade 1.0.4 -> 1.0.5
      exo: upgrade 0.12.8 -> 0.12.9
      gedit: add gsettings to inherit

Changqing Li (1):
      dnsmasq.conf: fix dnsmasq path

Denys Dmytriyenko (1):
      recipes: rename distro_features_check to features_check

Jan Luebbe (6):
      openct: merge do_install and do_install_append
      pcsc-lite: add support for native builds
      opensc: use pcsc-lite instead of openct by default
      opensc: add support for native builds
      libp11: add support for native builds
      softhsm: add recipe

Kai Kang (1):
      mariadb: replace dependency readline with libedit

Khem Raj (6):
      dlm: Drop -fstack-clash-protection for clang
      ruli: Fix install step and build samples too
      libkcapi: Update patch to upstream submitted one
      sanlock: Use python3 and add sanlock user/group
      sanlock: Replace cp -a with cp -R --no-dereference
      nodejs: libatomic patch should be target specific

Lei YU (1):
      googletest: move to release 1.10.0

Nicola Lunghi (4):
      python3-importlib-metadata: fix class-target overriding default dependencies
      python-configparser: Add native and nativesdk to BBCLASSEXTEND
      python-contextlib2: Add native and nativesdk to BBCLASSEXTEND
      python-scandir: Add native and nativesdk to BBCLASSEXTEND

Paul Barker (1):
      liblockfile: Rename patch (1):
      python-jsonschema: add missing dependency

Ross Burton (1):
      python-babel: add BBCLASSEXTEND for native/nativesdk

Rouven Czerwinski (1):
      python-pyelftools: add recipes

Stefan Agner (2):
      haveged: use the Fedora service file available from upstream
      networkmanager: do not deploy unnecessary udev rule file

Wang Mingyu (3):
      mcelog: upgrade 1.65 -> 1.66
      hwdata: upgrade 0.328 -> 0.329
      libdev-checklib-perl: upgrade 1.13 -> 1.14

Zang Ruochen (17):
      python-zopeinterface: upgrade 4.6.0 -> 4.7.1
      python-yappi: upgrade 0.98 -> 1.0
      python-xstatic: upgrade 1.0.1 -> 1.0.2
      python-xlrd: upgrade 1.1.0 -> 1.2.0
      python-urllib3: upgrade 1.25.6 -> 1.25.7
      python-tzlocal: upgrade 1.5.1 -> 2.0.0
      python-twitter: upgrade 3.7.0 -> 3.8.0
      python-twisted: upgrade 19.7.0 -> 19.10.0
      python3-meh: upgrade 0.47 -> 0.48
      python-pyephem: upgrade ->
      python3-pykickstart: upgrade 3.20 -> 3.22
      python-pyparted: upgrade 3.11.2 -> 3.11.3
      libextutils-cppguess-perl: upgrade 0.12 -> 0.20
      libmoo-perl: upgrade 2.003004 -> 2.003006
      libdbd-sqlite-perl: upgrade 1.62 -> 1.64
      libclass-method-modifiers-perl: upgrade 2.12 -> 2.13
      librole-tiny-perl: upgrade 2.000006 -> 2.001004 (2):
      gitpkgv.bbclass: Use --git-dir option
      gitpkgv.bbclass: Support also lightweight tags

Change-Id: I00fb24df7bb3849ed0c9337a66623d9b4cba5999
Signed-off-by: Brad Bishop <>
237 files changed
tree: 3fd23d8e51ed9b3e9c4aa01514aaf778674cad14
  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.