Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / e0e69beab7c268e4ad98972016c78b0d7d5769ac
commite0e69beab7c268e4ad98972016c78b0d7d5769ac[log] [tgz]
authorBrad Bishop <bradleyb@fuzziesquirrel.com>Wed Aug 29 22:27:08 2018 -0400
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Thu Aug 30 22:19:19 2018 -0400
treecea482bf755215d6c31fb9f64a5ecb963f1f450e
parentffd4e6d47eefbe4b71994f978f72b04af89eb97b [diff]
skeleton: srcrev bump 5da4f4fc17..d7a8ba5b58

Adriana Kobylak (5):
      fan_control: Move to using xyz.openbmc_project.Sensors
      configs: Remove BootProgressSensor
      configs: Remove the OperatingSystemStatus sensor
      configs: Remove BootCountSensor
      configs: Remove TurboAllowedSensor

Matt Spinler (16):
      Add function to load in the GPIO data from JSON.
      Add documentation on GPIO JSON
      Use cJSON to read the GPIO configuration
      Use cJSON to get the GPIO definitions
      Fill in function to convert GPIO pin to a number
      Fill in the function that finds the GPIO base
      Remove host control GPIOs from GpioConfigs
      Call gpio_inits_done() from GPIO consumers
      Remove unnecessary args from GPIO functions
      Point obmcutil chassiskill code at the GPIO JSON
      Remove the GPIOs from Witherspoon.py
      Remove the GPIOs from Zaius.py
      Remove the GPIOs from Lanyang.py
      Remove the GPIOs from Palmetto.py
      Remove the GPIOs from Romulus.py
      Remove the GPIOs from S2600wf.py

(From meta-phosphor rev: a3c2e523e1cd83b088cb70ccd6d3fdc697785c1f)

Change-Id: I847dfae765dfea67738bc93bd589621ab9249849
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: cea482bf755215d6c31fb9f64a5ecb963f1f450e
  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