Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 5b836875ac77c547088144909ba98f956ac0e90f
commit5b836875ac77c547088144909ba98f956ac0e90f[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Thu Sep 13 12:50:31 2018 +0000
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Thu Sep 13 16:35:28 2018 -0400
tree82a466392024d11600c18fac7bed6a4040f14fc1
parentb2f928d8476768098751935fc47feaff737094a6 [diff]
mboxbridge: srcrev bump acdbdd141e..41c337e88b

Andrew Jeffery (66):
      format-code: Look for clang-format-6.0 as well
      make: Improve cscope database quality
      mboxd_lpc_reset: Use SPDX licence header
      common: Include what we use in the header
      mboxctl: Remove redundant includes
      test: bmc_event_ack_v2 must negotiate v2
      dbus: Use consistent prefix for dbus function symbols
      dbus: Mark current command set as legacy
      dbus: Use new bus name, object and interface
      mboxctl: Switch to new DBus interface
      mboxd: Clean up dbus objects
      windows: Make set_window_bytemap return standard errno
      mboxd: Rename flash files
      flash: Rename header guard
      flash: Drop __cplusplus guard
      flash: Rename init_flash_dev to flash_dev_init
      flash: Rename free_flash_dev to flash_dev_free
      flash: Rename copy_flash to flash_copy
      flash: Rename set_flash_bytemap to flash_set_bytemap
      flash: Rename erase_flash to flash_erase
      flash: Rename write_flash to flash_write
      mboxd: Rename lpc source files
      lpc: Rename header-guard
      lpc: Drop __cplusplus guard
      lpc: Rename init_lpc_dev to lpc_dev_init
      lpc: Rename free_lpc_dev to lpc_dev_free
      lpc: Rename point_to_flash lpc_map_flash
      lpc: Rename point_to_memory to lpc_map_memory
      lpc: Rename reset_lpc to lpc_reset
      mboxd: Rename windows files
      windows: Rename header guard
      windows: Add WINDOWS prefix to FLUSH macros
      windows: Rename init_windows to windows_init
      windows: Rename free_windows to windows_free
      windows: Rename write_from_window* to window_flush*
      windows: Rename alloc_window_dirty_bytemap to windows_alloc_dirty_bytemap
      windows: Rename set_window_bytemap to window_set_bytemap
      windows: Rename close_current_window to windows_close_current
      windows: Rename reset_window to window_reset
      windows: Rename reset_all_windows to windows_reset_all
      windows: Rename find_oldest_window to windows_find_oldest
      windows: Rename find_largest_window to windows_find_largest
      windows: Rename search_windows to windows_search
      windows: Rename create_map_window to windows_create_map
      mboxd: Rename mboxd_msg to transport_mbox
      protocol: Add get_info
      protocol: Add reset
      protocol: Add get_flash_info
      protocol: Add create_read_window
      protocol: Add create_write_window
      protocol: Add mark_dirty
      protocol: Add erase
      protocol: Add flush
      protocol: Add close
      protocol: Add ack
      vpnor: Hijack protocol rather than transport
      transport: mbox: Centralise errno translation
      mboxd: Cleanup errnos not captured by tests
      transport: mbox: Drop handler functions from header
      flash: Move access rate estimate from transport header
      protocol: Provide abstraction over event notification
      transport: mbox: Rename dispatch_mbox to transport_mbox_dispatch
      transport: mbox: Rename *init_mbox_dev to *transport_mbox_init
      transport: mbox: Rename free_mbox_dev to transport_mbox_free
      mboxd: Refactor and rename mbox.h to mboxd.h
      windows: Always allocate a default-size dirty byte map

(From meta-phosphor rev: 1ac9bcd0abed292774aba7a78f309a3bc969485d)

Change-Id: I0884d707ad679d82a48db540a8881c8f955e83c5
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: 82a466392024d11600c18fac7bed6a4040f14fc1
  1. meta-arm/
  2. meta-aspeed/
  3. meta-evb/
  4. meta-ibm/
  5. meta-ingrasys/
  6. meta-intel/
  7. meta-inventec/
  8. meta-mellanox/
  9. meta-nuvoton/
  10. meta-openembedded/
  11. meta-openpower/
  12. meta-phosphor/
  13. meta-portwell/
  14. meta-qualcomm/
  15. meta-quanta/
  16. meta-raspberrypi/
  17. meta-security/
  18. meta-x86/
  19. poky/
  20. bitbake ⇨ poky/bitbake/
  21. LICENSE ⇨ poky/LICENSE
  22. meta ⇨ poky/meta
  23. meta-poky ⇨ poky/meta-poky/
  24. oe-init-build-env ⇨ poky/oe-init-build-env
  25. scripts ⇨ poky/scripts/
  26. .gitignore
  27. .gitreview
  28. .templateconf
  29. MAINTAINERS
  30. openbmc-env
  31. README.md
  32. 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 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. 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

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
  • POWER On Chip Controller (OCC) Support

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