meta-ibm: Add license information

When meta-ibm was split out as a subtree from openbmc the license
information was not copied to the new repository.

License of the metadata and code remains unchanged - this is only a
documentation update.

Fixes: 194ff4f1f5d44b12e9cb06ddafa6adb20174a13c
(From meta-ibm rev: 1bcd2f64f4fedd9a405db01160ef24d9a475e96d)

Change-Id: Id007b0cce2a199b4efbd8db2950cf4fc25d6b4fd
Signed-off-by: Brad Bishop <>
3 files changed
tree: 2aeef571d0bbf654b78424394e0f7cc39ca6767a
  1. meta-arm/
  2. meta-aspeed/
  3. meta-evb/
  4. meta-google/
  5. meta-ibm/
  6. meta-ingrasys/
  7. meta-intel/
  8. meta-inventec/
  9. meta-mellanox/
  10. meta-nuvoton/
  11. meta-openembedded/
  12. meta-openpower/
  13. meta-phosphor/
  14. meta-portwell/
  15. meta-qualcomm/
  16. meta-quanta/
  17. meta-raspberrypi/
  18. meta-security/
  19. meta-x86/
  20. poky/
  21. .gitignore
  22. .gitreview
  23. .templateconf
  25. openbmc-env
  27. 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 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
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

  • REST Management
  • IPMI
  • SSH based SOL
  • Power and Cooling Management
  • Event Logs
  • Zeroconf discoverable
  • Sensors
  • Inventory
  • LED Management
  • Host Watchdog
  • Simulation
  • Code Update Support for multiple BMC/BIOS images
  • POWER On Chip Controller (OCC) Support

Features In Progress

  • Full IPMI 2.0 Compliance with DCMI
  • Verified Boot
  • HTML5 Java Script Web User Interface

Features Requested but need help

  • OpenCompute Redfish Compliance
  • OpenBMC performance monitoring
  • cgroup user management and policies
  • Remote KVM
  • Remote USB
  • OpenStack Ironic Integration
  • QEMU enhancements

Finding out more

Dive deeper in to OpenBMC by opening the docs repository.