Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / 7cf6e966347cc04e7e5d89f2401bf844aba8dc8a
commit7cf6e966347cc04e7e5d89f2401bf844aba8dc8a[log] [tgz]
authorBrad Bishop <bradleyb@fuzziesquirrel.com>Tue Jan 29 20:41:11 2019 -0500
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Wed Jan 30 04:26:33 2019 +0000
tree074156e92f7dca8e71aeb8929655309327bf5df3
parentd25baecafc81aa3ecc2625337017099b9ad226e5 [diff]
meta-phosphor: refresh master: 80d39cecca..c531e38a57

Update meta-phosphor to master HEAD.

Andrew Geissler (12):
      dbus-sensors: srcrev bump e8b60d0bf0..b82c2a78c7
      entity-manager: srcrev bump bcf722e0ce..63845bfe69
      bmcweb: srcrev bump 7625cb81a6..da21df7cde
      phosphor-webui: srcrev bump a83cd057aa..7e48d0818a
      phosphor-ipmi-flash: srcrev bump 46bdadc210..13e49868de
      phosphor-fan-presence: srcrev bump f0b020fb32..a1aef7a100
      phosphor-hwmon: srcrev bump 9a7ef7c639..cd40c8815a
      phosphor-net-ipmid: srcrev bump 744b3c8b84..22c8a210c4
      phosphor-net-ipmid: srcrev bump 22c8a210c4..5f1dd316fc
      phosphor-net-ipmid: srcrev bump 5f1dd316fc..d5a4f45e1e
      phosphor-host-ipmid: srcrev bump 23df06f44f..f301f04567
      phosphor-objmgr: srcrev bump a82779fb66..d732287cdd

Change-Id: Ic03af27608cb33750e1d9d4765f521a39463762c
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
10 files changed
tree: 074156e92f7dca8e71aeb8929655309327bf5df3
  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-inspur/
  10. meta-intel/
  11. meta-inventec/
  12. meta-mellanox/
  13. meta-nuvoton/
  14. meta-openembedded/
  15. meta-openpower/
  16. meta-phosphor/
  17. meta-portwell/
  18. meta-qualcomm/
  19. meta-quanta/
  20. meta-raspberrypi/
  21. meta-security/
  22. meta-x86/
  23. meta-xilinx/
  24. poky/
  25. bitbake ⇨ poky/bitbake/
  26. LICENSE ⇨ poky/LICENSE
  27. meta ⇨ poky/meta
  28. meta-poky ⇨ poky/meta-poky/
  29. meta-skeleton ⇨ poky/meta-skeleton
  30. oe-init-build-env ⇨ poky/oe-init-build-env
  31. scripts ⇨ poky/scripts/
  32. .gitignore
  33. .gitreview
  34. .templateconf
  35. MAINTAINERS
  36. openbmc-env
  37. README.md
  38. 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
Romulusmeta-ibm/meta-romulus/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

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