Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / cdd3eeb67364079f46ad3f6571cb24423b601d02
commitcdd3eeb67364079f46ad3f6571cb24423b601d02[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Thu Jan 03 16:45:46 2019 +1030
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Sat Jan 05 17:31:53 2019 +0000
tree6fdc6f3afc52eacc8172168f83012255224f78da
parent7510c10beda1df31352780db993f1c07799fc54d [diff]
linux-aspeed: PECI subsystem and hwmon drivers

Jae Hyun Yoo (12):
      dt-bindings: Add a document of PECI subsystem
      Documentation: ioctl: Add ioctl numbers for PECI subsystem
      peci: Add support for PECI bus driver core
      dt-bindings: Add a document of PECI adapter driver for ASPEED AST24xx/25xx SoCs
      ARM: dts: aspeed: peci: Add PECI node
      peci: Add a PECI adapter driver for Aspeed AST24xx/AST25xx
      dt-bindings: mfd: Add a document for PECI client MFD
      mfd: intel-peci-client: Add PECI client MFD driver
      Documentation: hwmon: Add documents for PECI hwmon client drivers
      hwmon: Add PECI cputemp driver
      hwmon: Add PECI dimmtemp driver
      Add maintainers for the PECI subsystem

Joel Stanley (1):
      ARM: config: aspeed: Add PECI drivers

(From meta-aspeed rev: c9793688e3358ba1fb1aab7b10fc16112bbb1614)

Change-Id: Ic109bc0caf5e3e13fd4d026f787c256f72353cf0
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: 6fdc6f3afc52eacc8172168f83012255224f78da
  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