Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / 39803765763df44c3e6fd456d652cb21bae3c628
commit39803765763df44c3e6fd456d652cb21bae3c628[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Tue Jan 22 17:31:53 2019 +0000
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Wed Jan 23 14:08:21 2019 +0000
tree321d7b17082782e737450effbf944d3a88d32126
parent9fb6abbc374e6decc9fc2dedde3f8a50a6d3c231 [diff]
phosphor-ipmi-flash: srcrev bump f9566d88d4..46bdadc210

Patrick Venture (22):
      tools: specify common ipmi errors for humans
      firmware: reorder open cases slightly
      rename lpcmapperinterface to hardwaremapperinterface
      hardware interface: add copyFrom
      lpc: add missing headers
      rename lpc_mapper_mock -> window_mapper_mock
      lpc_aspeed: move driver path to class member
      lpc mappers: provide BMC memory address for mapping
      lpc_aspeed: add mapped file descriptor
      window interface: add close method
      lpc_aspeed: implement mapRegion as part of copyFrom
      lpc_aspeed: implement close method
      lpc_aspeed: implement copyFrom
      tools: blob add writeMeta to interface
      lpc_handler: add missing TODO
      tools: lpc: start implementation, send metadata
      tools: minor cleanup, drop member return inline
      tools: lpc: add internal/sys to handler
      lpc_aspeed: delete copy/assignment of object
      tools: lpc configuration structure is packed
      tools: add io interface for mmio, etc
      tools: tie devmem io handler into lpc handler

(From meta-phosphor rev: 2c4dede0ad2d21839cd1fab239bc92ead4505c3f)

Change-Id: I083753a65b10bc2a42a632f2f828ee40f8c490ec
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: 321d7b17082782e737450effbf944d3a88d32126
  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