Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / 9dc05e540e8510851b7631c5fca57dcec4a35990
commit9dc05e540e8510851b7631c5fca57dcec4a35990[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Tue Oct 10 15:47:33 2017 +1030
committerJoel Stanley <joel@jms.id.au>Tue Oct 10 15:47:33 2017 +1030
treeb504c4b3b063098b1bf2aa2f7222182936a7abb7
parentf5952ed1ab643a31ac014f8455d81f28330573b0 [diff]
kernel: FSI SBEFIFO and OCC rework

Edward A. James (32):
      Revert "drivers/hwmon/occ: Add temperature fault attribute and VRM temp alarm"
      fsi: sbefifo: Fix includes
      fsi: sbefifo: Use a defined reschedule length
      fsi: sbefifo: Use __be32 for big endian values
      fsi: sbefifo: white space fixes
      fsi: sbefifo: replace awkward wait_event expression
      fsi: sbefifo: remove redundant function
      fsi: sbefifo: Use goto to reduce put statements
      fsi: sbefifo: Do an earlier get_client call
      fsi: sbefifo: Remove warning and user data access check
      fsi: sbefifo: destroy the ida list on exit
      fsi: sbefifo: Fix module authors and comments
      fsi: sbefifo: Fix include guards in header file
      fsi: SBEFIFO: Fix probe() and remove()
      fsi: SBEFIFO: check for xfr complete in read wait_event
      fsi: occ: Fix includes
      fsi: occ: Fix errant kfree calls
      fsi: occ: remove unused occ_command structure
      fsi: occ: Use big-endian values
      fsi: occ: Return ENODEV if client is NULL
      fsi: occ: Remove early user buffer checking
      fsi: occ: Switch to more logical errnos
      fsi: occ: fix white space and bracket problems
      fsi: occ: Destroy the ida list on exit
      fsi: occ: Remove unnecessary platform_set_drvdata call
      fsi: occ: Add comments for clarity
      fsi: occ: Add OCC response definitions to header
      fsi: occ: Poll while receiving "command in progress"
      fsi: occ: Add cancel to remove() and fix probe()
      fsi: occ: Fix client memory management
      hwmon: (occ) Remove repeated ops for OCC command in progress
      drivers: hwmon: occ: Cancel occ operations in remove()

Change-Id: I5cb766b536070495a726567a675613d7f035e7bd
Signed-off-by: Joel Stanley <joel@jms.id.au>
1 file changed
tree: b504c4b3b063098b1bf2aa2f7222182936a7abb7
  1. import-layers/
  2. meta-openbmc-bsp/
  3. meta-openbmc-machines/
  4. meta-phosphor/
  5. bitbake ⇨ import-layers/yocto-poky/bitbake
  6. documentation ⇨ import-layers/yocto-poky/documentation
  7. LICENSE ⇨ import-layers/yocto-poky/LICENSE
  8. meta ⇨ import-layers/yocto-poky/meta
  9. meta-poky ⇨ import-layers/yocto-poky/meta-poky
  10. meta-selftest ⇨ import-layers/yocto-poky/meta-selftest
  11. meta-skeleton ⇨ import-layers/yocto-poky/meta-skeleton
  12. meta-yocto-bsp ⇨ import-layers/yocto-poky/meta-yocto-bsp
  13. oe-init-build-env ⇨ import-layers/yocto-poky/oe-init-build-env
  14. oe-init-build-env-memres ⇨ import-layers/yocto-poky/oe-init-build-env-memres
  15. scripts ⇨ import-layers/yocto-poky/scripts
  16. .gitignore
  17. .gitreview
  18. .templateconf
  19. openbmc-env
  20. README.md
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, Open-Embedded, Systemd and DBus 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. OpenBMC has placed all known hardware targets in a standard directory structure meta-openbmc-machines/meta-openpower/[company]/[target]. You can see all of the known targets with find meta-openbmc-machines -type d -name conf. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet

MachineTEMPLATECONF
Palmettometa-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf
Barreleyemeta-openbmc-machines/meta-openpower/meta-rackspace/meta-barreleye/conf
Zaiusmeta-openbmc-machines/meta-openpower/meta-ingrasys/meta-zaius/conf
Witherspoonmeta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/conf

As an example target Palmetto

export TEMPLATECONF=meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf

3) 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 a 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

Features In Progress

  • Code Update Support for multiple BMC/BIOS images
  • POWER On Chip Controller (OCC) Support
  • 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