Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / aa9c0e7e322b6f9eb7a59c6fa9531d2c529889ef
commitaa9c0e7e322b6f9eb7a59c6fa9531d2c529889ef[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Mon Oct 29 15:50:27 2018 +0000
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Mon Oct 29 20:15:40 2018 -0400
treed0df4e91e8fe139adfced5c7a9c19aa41d01577e
parentb793bc40c58bdf5f7dc4bb6785d4dff97c2c33ae [diff]
ipmi-fru-parser: srcrev bump 5c787214b1..19bea9ae44

Patrick Venture (22):
      writefrudata: drop function parameter set
      readeeprom: use log error instead of fprintf(stderr)
      types: fixup header
      frup: add missing header
      writefrudata: cleanup header
      writefrudata: add function header
      style: apply naming convention to ipmi_validate_fru_area
      style: rename cleanup_error, move into anonymous
      style: move getFRUValue into anonymous namespace
      style: move getService into anonymous namespace
      style: rename update_inventory, move into anonymous
      writefrudata.cpp: fixup variable shadowing
      writefrudata: add missing header: map
      writefrudata.cpp: add header for file
      writefrudata: drop unused dynamic linking header
      writefrudata: drop unused lib mapper header
      ipmi_fru: drop unused member functions
      ipmi_fru: drop unused sd_bus pointer
      ipmi_fru: Rename to IPMIFruArea
      writefrudata.cpp: drop unused, add used header
      rename header: fru-area.hpp to fru_area.hpp
      cleanup: rename fru_area_vec_t type and use using

(From meta-phosphor rev: 70be299f7b635c27ab91cc3c83875f6cd9d5ad65)

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