Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / ba6de43c25453413491a8bac2d6f7f7011c9b326
commitba6de43c25453413491a8bac2d6f7f7011c9b326[log] [tgz]
authorBrad Bishop <bradleyb@fuzziesquirrel.com>Tue May 21 08:07:33 2019 -0400
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Tue May 21 08:07:37 2019 -0400
tree566a4990318c50f8b73e7cf43012eb1705e82d09
parent0e04b2e9b4857f65a89e16d3c14e16166b2cd8ea [diff]
meta-openembedded: subtree update:1ecd8b4364..f3018013ff

Adrian Bunk (1):
      Add irda-utils

Khem Raj (1):
      openocd: Upgrade to latest git version

Martin Jansa (8):
      gtkwave: add distro_features_check
      ndctl: make MACHINE_ARCH and ignore from libblockdev
      oprofile: make MACHINE_ARCH
      umip: make MACHINE_ARCH
      mscgen: fix SRC_URI for multilib
      python-cassandra-driver.inc: fix DEPENDS
      triggerhappy: fix issues
      opencv: use the same package name in PACKAGES and RDEPENDS

Oleksandr Kravchuk (4):
      znc: update to 1.7.3
      pure-ftpd: update to 1.0.47
      xl2tpd: update to 1.3.14
      ell: remove recipe

Scott Ellis (1):
      wireguard: Upgrade 20190123 -> 20190406

Tom Rini (1):
      toybox: Re-order inherit location so we can override do_configure

Zang Ruochen (8):
      python-pyparsing: upgrade 2.2.0 -> 2.4.0
      python-six: upgrade 1.11.0 -> 1.12.0
      python-typing: upgrade 3.6.4 -> 3.6.6
      python-urllib3: upgrade 1.23 -> 1.25.2
      python-wrapt: upgrade 1.10.11 -> 1.11.1
      python-mako:upgrade 1.0.9 -> 1.0.10
      python-pip: upgrade 19.1 -> 19.1.1
      python-pysocks: upgrade 1.6.8 -> 1.7.0

Change-Id: I9a4d8fb60195b1cfd0f39cebf8b113b3bb63808d
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
46 files changed
tree: 566a4990318c50f8b73e7cf43012eb1705e82d09
  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-mellanox/
  14. meta-nuvoton/
  15. meta-openembedded/
  16. meta-openpower/
  17. meta-phosphor/
  18. meta-portwell/
  19. meta-qualcomm/
  20. meta-quanta/
  21. meta-raspberrypi/
  22. meta-security/
  23. meta-x86/
  24. meta-xilinx/
  25. poky/
  26. bitbake ⇨ poky/bitbake/
  27. LICENSE ⇨ poky/LICENSE
  28. meta ⇨ poky/meta
  29. meta-poky ⇨ poky/meta-poky/
  30. meta-skeleton ⇨ poky/meta-skeleton
  31. oe-init-build-env ⇨ poky/oe-init-build-env
  32. scripts ⇨ poky/scripts/
  33. .gitignore
  34. .gitreview
  35. .templateconf
  36. MAINTAINERS
  37. openbmc-env
  38. README.md
  39. setup
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, 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 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. 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

MachineTEMPLATECONF
Palmettometa-ibm/meta-palmetto/conf
Zaiusmeta-ingrasys/meta-zaius/conf
Witherspoonmeta-ibm/meta-witherspoon/conf
Romulusmeta-ibm/meta-romulus/conf

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.

Contact