Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / b5c2fac1cadbbc307d6518f73d969bbc9e1c697b
commitb5c2fac1cadbbc307d6518f73d969bbc9e1c697b[log] [tgz]
authorRamesh Iyyar <rameshi1@in.ibm.com>Mon Dec 07 06:46:45 2020 -0600
committerAndrew Geissler <geissonator@yahoo.com>Thu Dec 17 12:21:07 2020 -0600
tree3b1c9b6e1e4e764fe862183b47a438f3690a2ee8
parentfa949ee7048a116d7656db1f812b384b4b2b03d7 [diff]
dump: Used renamed build option

- The phosphor-debug-collector renamed "host-dump-offload-transport" build
  option into "host-transport" to make generic for supporting other host
  dump action (i.e create,delete) not only offload so, changed build option
  here as well based on phosphor-debug-collector.

- In this patch bumping "phosphor-dbus-interfaces" as well to get
  bumped "phosphor-debug-collector" dependent dbus changes.

- Modified "ffdc" recipe to use phosphor-debug-collector.inc to avoid version
  update in two different place

Version bump info:

- phosphor-dbus-interfaces: SRCREV: 02f196d..a3943e6

    Dhruvaraj Subhashchandran (1):
      Update Create interface to return object path.

- phosphor-debug-collector: SRCREV: ff9c452..2279386

    Dhruvaraj Subhashchandran (2):
      Return the object path for user requested dumps.
      Progress tracking support for dump entries.

    Ramesh Iyyar (4):
      host-dump: Renamed host-dump-offload-transport build option
      offload: Moved existing pldm offload as oem/ibm command
      ibm-host-system-dump-offload: Used CustomFd
      host: Added support to delete system dump

phosphor-debug-collector patch:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-debug-collector/+/38792

(From meta-phosphor rev: 17743ee6f06480be7806d64d50f6bda1a2d4f5df)

Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com>
Change-Id: I54e01c192170b710977aa54439a02044a34e481e
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
4 files changed
tree: 3b1c9b6e1e4e764fe862183b47a438f3690a2ee8
  1. .github/
  2. meta-amd/
  3. meta-arm/
  4. meta-aspeed/
  5. meta-bytedance/
  6. meta-evb/
  7. meta-facebook/
  8. meta-google/
  9. meta-hpe/
  10. meta-hxt/
  11. meta-ibm/
  12. meta-ingrasys/
  13. meta-inspur/
  14. meta-intel/
  15. meta-inventec/
  16. meta-lenovo/
  17. meta-mellanox/
  18. meta-microsoft/
  19. meta-nuvoton/
  20. meta-openembedded/
  21. meta-openpower/
  22. meta-phosphor/
  23. meta-portwell/
  24. meta-qualcomm/
  25. meta-quanta/
  26. meta-raspberrypi/
  27. meta-security/
  28. meta-x86/
  29. meta-xilinx/
  30. meta-yadro/
  31. poky/
  32. bitbake ⇨ poky/bitbake/
  33. LICENSE ⇨ poky/LICENSE
  34. meta ⇨ poky/meta
  35. meta-poky ⇨ poky/meta-poky/
  36. meta-skeleton ⇨ poky/meta-skeleton
  37. oe-init-build-env ⇨ poky/oe-init-build-env
  38. scripts ⇨ poky/scripts/
  39. .gitignore
  40. .gitreview
  41. .templateconf
  42. MAINTAINERS
  43. openbmc-env
  44. README.md
  45. 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 perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum
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 set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called setup and takes the name of your hardware target as an argument.

The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:

$ . setup <machine> [build_dir]
Target machine must be specified. Use one of:

centriq2400-rep         nicole                     stardragon4800-rep2
f0b                     olympus                    swift
fp5280g2                olympus-nuvoton            tiogapass
gsj                     on5263m5                   vesnin
hr630                   palmetto                   witherspoon
hr855xg2                qemuarm                    witherspoon-128
lanyang                 quanta-q71l                witherspoon-tacoma
mihawk                  rainier                    yosemitev2
msn                     romulus                    zaius
neptune                 s2600wf

Once you know the target (e.g. romulus), source the setup script as follows:

. setup romulus build

For evb-ast2500, please use the below command to specify the machine config, because the machine in meta-aspeed layer is in a BSP layer and does not build the openbmc image.

TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env

4) Build

bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

OpenBMC Development

The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here

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.

Questions

First, please do a search on the internet. There's a good chance your question has already been asked.

For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.

For technical discussions, please see contact info below for Discord and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or Discord.

Features of OpenBMC

Feature List

  • Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
  • Full IPMI 2.0 Compliance with DCMI
  • Code Update Support for multiple BMC/BIOS images
  • Web-based user interface
  • REST interfaces
  • D-Bus based interfaces
  • SSH based SOL
  • Remote KVM
  • Hardware Simulation
  • Automated Testing
  • User management
  • Virtual media

Features In Progress

  • OpenCompute Redfish Compliance
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Technical Steering Committee

The Technical Steering Committee (TSC) guides the project. Members are:

  • Brad Bishop (chair), IBM
  • Nancy Yuen, Google
  • Sai Dasari, Facebook
  • James Mihm, Intel
  • Sagar Dharia, Microsoft
  • Supreeth Venkatesh, Arm

Contact