Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / 5dd7cbb3457c90724fc442b15bab2082d82b560a
commit5dd7cbb3457c90724fc442b15bab2082d82b560a[log] [tgz]
authorBrad Bishop <bradleyb@fuzziesquirrel.com>Wed Sep 05 22:26:40 2018 -0700
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Tue Sep 11 20:48:09 2018 +0000
tree368ed59906a1874f33a3a4a44fbb2f544013dc0a
parent3b32a97b1b171ca776a24454d22c1c59fc7bfa00 [diff]
poky: sumo refresh 45ef387cc5..51872d3f99

Update poky to sumo HEAD.

Awais Belal (8):
      bitbake: toaster: allow pokydirname to be evaluated when all layers are local
      bitbake: toaster: use a more flexible way to find bitbake
      bitbake: bitbake: toaster: allow TOASTER_DIR to be overridden from cmdline
      bitbake: toaster/widgets.py: avoid divide by zero issues
      bitbake: toastergui/newproject.html: fix release divs
      bitbake: toaster/checksettings: allow CUSTOM_XML_ONLY setting through env
      bitbake: toaster/models.py: allow local paths for custom recipe's base
      bitbake: toaster/layerdetails.js: don't hide local layer info

Karsten Strand (1):
      bitbake: bitbake: toaster: Fix comparison in recipe template

Change-Id: I8dbcad1d98ff8d3c660563781d887a2c91db5bf2
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
8 files changed
tree: 368ed59906a1874f33a3a4a44fbb2f544013dc0a
  1. meta-arm/
  2. meta-aspeed/
  3. meta-evb/
  4. meta-ibm/
  5. meta-ingrasys/
  6. meta-intel/
  7. meta-inventec/
  8. meta-mellanox/
  9. meta-nuvoton/
  10. meta-openembedded/
  11. meta-openpower/
  12. meta-phosphor/
  13. meta-portwell/
  14. meta-qualcomm/
  15. meta-quanta/
  16. meta-raspberrypi/
  17. meta-security/
  18. meta-x86/
  19. poky/
  20. bitbake ⇨ poky/bitbake/
  21. LICENSE ⇨ poky/LICENSE
  22. meta ⇨ poky/meta
  23. meta-poky ⇨ poky/meta-poky/
  24. oe-init-build-env ⇨ poky/oe-init-build-env
  25. scripts ⇨ poky/scripts/
  26. .gitignore
  27. .gitreview
  28. .templateconf
  29. MAINTAINERS
  30. openbmc-env
  31. README.md
  32. 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 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 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

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
  • BMC RAS

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.

Contact