Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / 39db0daec02390cd24e710bed260a0b27aab7531
commit39db0daec02390cd24e710bed260a0b27aab7531[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Mon Sep 09 02:20:54 2024 -0500
committerAndrew Geissler <geissonator@yahoo.com>Wed Sep 11 12:40:08 2024 +0000
treeb4b4671d0d28c1ae5bd286732bdbeb6beb221cfc
parent3a5454ad6853ef5ede2b8148f082644dbac3c0c5 [diff]
libpldm: srcrev bump 3559aa1fb3..435c9321fc

Andrew Jeffery (25):
      libpldm: Release v0.9.0
      meson: Format build files with `meson format`
      scripts: pre-submit: Run release buildtype tests under valgrind
      scripts: apply-renames: Update default clang version to 18
      checklists: releases: Add note about moving evolutions
      libpldm: Release v0.9.1
      bios_table: Remove pldm_bios_table_append_pad_checksum_check()
      bios_table: Remove pldm_bios_table_attr_entry_enum_decode_def_num_check()
      bios_table: Remove pldm_bios_table_attr_entry_enum_decode_pv_hdls_check()
      bios_table: Remove pldm_bios_table_attr_entry_enum_decode_pv_num_check()
      bios_table: Remove pldm_bios_table_attr_entry_enum_encode_check()
      bios_table: Remove pldm_bios_table_attr_entry_integer_encode_check()
      bios_table: Remove pldm_bios_table_attr_entry_string_decode_def_string_length_check()
      bios_table: Remove pldm_bios_table_attr_entry_string_encode_check()
      bios_table: Remove pldm_bios_table_attr_value_entry_encode_enum_check()
      bios_table: Remove pldm_bios_table_attr_value_entry_encode_integer_check()
      bios_table: Remove pldm_bios_table_attr_value_entry_encode_string_check()
      bios_table: Remove pldm_bios_table_string_entry_decode_string_check()
      bios_table: Remove pldm_bios_table_string_entry_encode_check()
      pdr: Remove pldm_entity_association_pdr_add_check()
      pdr: Remove pldm_entity_association_pdr_add_from_node_check()
      pdr: Remove pldm_pdr_add_check()
      pdr: Remove pldm_pdr_add_fru_record_set_check()
      fru: Remove get_fru_record_by_option_check()
      scripts: Symlink pre-submit to run-ci

Change-Id: I191d46f7598d0b4242950eb558bbb6cc88916ff0
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
1 file changed
tree: b4b4671d0d28c1ae5bd286732bdbeb6beb221cfc
  1. .github/
  2. meta-amd/
  3. meta-ampere/
  4. meta-arm/
  5. meta-aspeed/
  6. meta-asrock/
  7. meta-bytedance/
  8. meta-delta/
  9. meta-evb/
  10. meta-facebook/
  11. meta-fii/
  12. meta-google/
  13. meta-hpe/
  14. meta-ibm/
  15. meta-ieisystem/
  16. meta-ingrasys/
  17. meta-intel-openbmc/
  18. meta-inventec/
  19. meta-nuvoton/
  20. meta-openembedded/
  21. meta-openpower/
  22. meta-phosphor/
  23. meta-qualcomm/
  24. meta-quanta/
  25. meta-raspberrypi/
  26. meta-security/
  27. meta-supermicro/
  28. meta-tyan/
  29. meta-ufispace/
  30. meta-wistron/
  31. meta-yadro/
  32. poky/
  33. .templateconf ⇨ poky/.templateconf
  34. bitbake ⇨ poky/bitbake/
  35. LICENSE ⇨ poky/LICENSE
  36. meta ⇨ poky/meta
  37. oe-init-build-env ⇨ poky/oe-init-build-env
  38. scripts ⇨ poky/scripts/
  39. .eslintrc.json
  40. .gitignore
  41. .gitreview
  42. openbmc-env
  43. OWNERS
  44. README.md
  45. setup
README.md

OpenBMC

Build Status

OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your platform.

Setting up your OpenBMC project

1) Prerequisite

See the Yocto documentation for the latest requirements

Ubuntu

sudo apt install git python3-distutils gcc g++ make file wget \
    gawk diffstat bzip2 cpio chrpath zstd lz4 bzip2

Fedora

sudo dnf install git python3 gcc g++ gawk which bzip2 chrpath cpio \
    hostname file diffutils diffstat lz4 wget zstd rpcgen patch

2) Download the source

git clone https://github.com/openbmc/openbmc
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:
...

A more complete list of supported machines can be found under meta-phosphor/docs.

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

. setup romulus

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.

Will OpenBMC run on my Acme Server Corp. XYZ5000 motherboard?

This is a common question, particularly regarding boards from popular COTS (commercial off-the-shelf) vendors such as Supermicro and ASRock. You can see the list of supported boards by running . setup (with no further arguments) in the root of the OpenBMC source tree. Most of the platforms supported by OpenBMC are specialized servers operated by companies running large datacenters, but some more generic COTS servers are supported to varying degrees.

If your motherboard is not listed in the output of . setup it is not currently supported. Porting OpenBMC to a new platform is a non-trivial undertaking, ideally done with the assistance of schematics and other documentation from the manufacturer (it is not completely infeasible to take on a porting effort without documentation via reverse engineering, but it is considerably more difficult, and probably involves a greater risk of hardware damage).

However, even if your motherboard is among those listed in the output of . setup, there are two significant caveats to bear in mind. First, not all ports are equally mature -- some platforms are better supported than others, and functionality on some "supported" boards may be fairly limited. Second, support for a motherboard is not the same as support for a complete system -- in particular, fan control is critically dependent on not just the motherboard but also the fans connected to it and the chassis that the board and fans are housed in, both of which can vary dramatically between systems using the same board model. So while you may be able to compile and install an OpenBMC build on your system and get some basic functionality, rough edges (such as your cooling fans running continuously at full throttle) are likely.

See also "Supported Machines".

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:

  • Benjamin Fair, Google
  • Patrick Williams, Meta
  • Roxanne Clarke, IBM
  • Sagar Dharia, Microsoft
  • Samer El-Haj-Mahmoud, Arm
  • Terry Duncan, Intel

Contact