Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / 174e11403947351aff607e626cb548d7f5b2b403
commit174e11403947351aff607e626cb548d7f5b2b403[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Fri Sep 14 23:00:21 2018 +0000
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Mon Sep 17 08:59:22 2018 -0400
treede848f4d8851e693e400c2cc35aa929f6f1f0389
parent279e2515bf316c7f6baff39df8c6dffb396d7636 [diff]
mboxbridge: srcrev bump 41c337e88b..93c8edc9a0

Andrew Jeffery (20):
      transport: dbus: Add get_info
      transport: Switch transports as required on GET_MBOX_INFO
      daemon: Remove the concept of triggering or suppressing events
      transport: Retain knowledge of setting and clearing of events
      transport: dbus: Handle events
      transport: Rework BMC event handling
      transport: dbus: Implement reset
      transport: dbus: Implement ack
      transport: dbus: Implement get_flash_info
      transport: dbus: Implement create_read_window
      transport: dbus: Implement create_write_window
      transport: dbus: Implement close
      transport: dbus: Implement mark_dirty
      transport: dbus: Implement flush
      transport: dbus: Implement erase
      windows: Include stdbool.h
      test: Add windows_equally_evictable
      control: Add FIXME in reset handling
      vpnor: pnor_partition: Debugging for Request.fulfil()
      Documentation: Rewrite protocol specification

(From meta-phosphor rev: 9bf99183ff4eb33081e86188d5179bfb579f18d9)

Change-Id: I8007e879bfa294861369b2ec9201c9517a602107
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: de848f4d8851e693e400c2cc35aa929f6f1f0389
  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. bitbake ⇨ poky/bitbake/
  22. LICENSE ⇨ poky/LICENSE
  23. meta ⇨ poky/meta
  24. meta-poky ⇨ poky/meta-poky/
  25. oe-init-build-env ⇨ poky/oe-init-build-env
  26. scripts ⇨ poky/scripts/
  27. .gitignore
  28. .gitreview
  29. .templateconf
  30. MAINTAINERS
  31. openbmc-env
  32. README.md
  33. 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