Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / owners-plugin-test / 502ed4c0f99c2cc94928ffda3050ee5ef94cacbe
commit502ed4c0f99c2cc94928ffda3050ee5ef94cacbe[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Tue Dec 12 13:27:13 2017 +1030
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Tue Dec 12 04:16:15 2017 +0000
tree415318a7a57450a0ae66b05cacd7b2a325a3eb8e
parentf3713c5ea4c9b8dce131b8ed4a7f6765485210e1 [diff]
kernel: Add Intel S2600WF, gpio and pinctrl fixes, machine updates

Andrew Jeffery (2):
      ARM: dts: aspeed: Ensure platform mux RMII1 for MAC0
      pinctrl: aspeed: Rework strap register write logic for the AST2500

James Feist (2):
      ARM: dts: aspeed: Rename aspeed-bmc-opp-flash-layout.dtsi
      ARM: dts: Add S2600WF BMC Machine

Lei YU (1):
      ARM: dts: aspeed: P8: Add checkstop gpio key

Patrick Venture (6):
      ARM: dts: aspeed: gpio controller register range
      ARM: dts: aspeed: quanta: add aliases for i2c pcie
      ARM: dts: aspeed: quanta-q71l: move coin battery sensor
      ARM: dts: aspeed: zaius: move coin battery sensor
      ARM: dts: aspeed-g4: add serial gpio driver entry
      ARM: dts: aspeed: quanta: add i2cmux for frus

Peter Hanson (1):
      ARM: dts: quanta: i2c-2 idle disconnects

Rick Altherr (1):
      pinctrl: aspeed: Allow disabling Port D and Port E loopback mode

Vishwanatha Subbanna (1):
      ARM: dts: aspeed: witherspoon: Add power-button LED

Yong Li (1):
      pinctrl: aspeed: Fix ast2500 strap register write logic

Change-Id: I960b2c28eb0f0e0af055ea0ecdf48e01256c2f14
Signed-off-by: Joel Stanley <joel@jms.id.au>
2 files changed
tree: 415318a7a57450a0ae66b05cacd7b2a325a3eb8e
  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