Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / 790286f1ad7ef8364f524477ef459bfa828e2e05
commit790286f1ad7ef8364f524477ef459bfa828e2e05[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Tue Oct 23 01:40:17 2018 +0000
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Tue Oct 23 13:29:39 2018 -0400
tree2a84eb37ef80aed97f549edcd756a12eb851252b
parent08589c246f425a055e3295d8f4bbbb89816bacc1 [diff]
entity-manager: srcrev bump b5e32c2396..28dc2dae9f

Cezary Golder (1):
      Add gpio instances for WFP Baseboard

Ed Tanous (1):
      Implement the 2UX16 riser correctly

Jae Hyun Yoo (1):
      Replace apply_visitor() calls with visit()

James Feist (11):
      Upgrade to 17 standard
      Add delete object method
      Add Pid Zone Schema
      Remove empty frus from results
      Add PWM configurations to Chassis
      [fru-device] remove dependency on i2c-dev-user
      Stop using mapbox directly
      Add intial stepwise configuration example
      Add gpio properties
      Bump sdbusplus
      Don't allow hex strings on d-bus

(From meta-phosphor rev: 597c3d0d9fe4d585c44c8cf58f6f0be4bb11262b)

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