Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / 1b2908fe677a3d46de1a1318013281fda2793af4
commit1b2908fe677a3d46de1a1318013281fda2793af4[log] [tgz]
authorSantosh Puranik <santosh.puranik@in.ibm.com>Tue May 07 14:45:50 2019 +0530
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Thu May 23 14:58:07 2019 -0400
tree646ea819f75c39e5badc68e76102e221ac4e8aa8
parente9b0fe9e17d4fa69d3eecf7e48243308aa05f240 [diff]
Accelerator interface for sensorinventory items

This commit adds the xyz.openbmc_project.inventory.Item.Accelerator
interface to GPU inventory items. This is needed so that the inventory
DBUS objects can be queried based on the interface they implement
(using the mapper).

Changes made to merge_yamls script to support interfaces that contain
no properties. This will need a corresponding change in the
phosphor-host-ipmi repo to support empty DBUS interfaces.
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-host-ipmid/+/21106

Tested:
Verified that the merged YAML file containing sensor config information
has now an empty interface xyz.openbmc_project.Inventory.Item.Accelerator
for the GV100 GPU sensors.

(From meta-phosphor rev: f510f7b6b708b22db1f08faf369994f01edd0ddc)

Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com>
Change-Id: I213c4af2e5b09b8a9cd5d37409f37fc7c075a013
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2 files changed
tree: 646ea819f75c39e5badc68e76102e221ac4e8aa8
  1. .github/
  2. meta-arm/
  3. meta-aspeed/
  4. meta-evb/
  5. meta-facebook/
  6. meta-google/
  7. meta-hxt/
  8. meta-ibm/
  9. meta-ingrasys/
  10. meta-inspur/
  11. meta-intel/
  12. meta-inventec/
  13. meta-mellanox/
  14. meta-nuvoton/
  15. meta-openembedded/
  16. meta-openpower/
  17. meta-phosphor/
  18. meta-portwell/
  19. meta-qualcomm/
  20. meta-quanta/
  21. meta-raspberrypi/
  22. meta-security/
  23. meta-x86/
  24. meta-xilinx/
  25. poky/
  26. bitbake ⇨ poky/bitbake/
  27. LICENSE ⇨ poky/LICENSE
  28. meta ⇨ poky/meta
  29. meta-poky ⇨ poky/meta-poky/
  30. meta-skeleton ⇨ poky/meta-skeleton
  31. oe-init-build-env ⇨ poky/oe-init-build-env
  32. scripts ⇨ poky/scripts/
  33. .gitignore
  34. .gitreview
  35. .templateconf
  36. MAINTAINERS
  37. openbmc-env
  38. README.md
  39. 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 perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum
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

  • Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
  • Full IPMI 2.0 Compliance with DCMI
  • Code Update Support for multiple BMC/BIOS images
  • Web-based user interface
  • REST interfaces
  • D-Bus based interfaces
  • SSH based SOL
  • Remote KVM
  • Hardware Simulation
  • Automated Testing

Features In Progress

  • OpenCompute Redfish Compliance
  • User management
  • Virtual media
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Contact