|author||Andrew Geissler <firstname.lastname@example.org>||Wed May 10 11:40:39 2023 -0500|
|committer||Andrew Geissler <email@example.com>||Fri May 19 18:14:24 2023 +0000|
openpower-occ-control: srcrev bump 11fd1314ab..a49c987eeb Andrew Geissler (1): sdbusplus:p10: object: don't use 'bool' argument constructor Ben Tyner (1): Add support for power mode locking Chris Cain (19): Create PowerMode object before status objects Queue active sensor updates before status objs created Ensure occActive called after device enabled Prevent repeatedly reading PLDM sensors when proc garded Prevent using stale data when active sensors were queued Restart discover timer to ensure recovery is attempted Reuse MCTP instance IDs for PLDM retries Fix correlation between OCC StateSensorPDRs and procs Revert clearing PDRs if host power is off Validate user power cap changes fall within limits Re-fetch StateSensors if unable to find sensor Commit OCC related errors as informational Add journal traces to occ-control PELs Move the service files to the occ-control repo Remove Hypervisor check for PowerVM target Trace PLDM response on unexpected states Check host state before attempting OCC communication Handle OCC active sensor updates prior to host runtime Add Chris as maintainer Eddie James (5): Switch to setting Device active Log a PEL for communication, presence mismatch, and safe state errors Provide a fmtlib ostream formatter for SysPwrMode enum Update fmtlib fix Use format_as rather than operator << overload Patrick Williams (11): OWNERS: switch 'matches' to 'matchers' sdbusplus: use shorter type aliases MAINTAINERS: remove file yaml: move to subdirectory python: fix flake8 warnings and format with black beautysh: re-format meson: change dependency order for subproject build meson: add dependency for nlohmann-json meson: remove deprecated get_pkgconfig_variable regenerate-meson: re-run with latest from sdbusplus clang-format: copy latest and re-format Sheldon Bailey (3): failure to get OCC temp 0 Fix Max fan speed with Deconfigured DIMM Add safe mode to user interface Change-Id: I2898bd260f537d9efb0c08b8550dad0732666bb1 Signed-off-by: Andrew Geissler <firstname.lastname@example.org>
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.
See the Yocto documentation for the latest requirements
sudo apt install git python3-distutils gcc g++ make file wget \ gawk diffstat bzip2 cpio chrpath zstd lz4 bzip2
sudo dnf install git python3 gcc g++ gawk which bzip2 chrpath cpio \ hostname file diffutils diffstat lz4 wget zstd rpcgen patch
git clone https://github.com/openbmc/openbmc cd openbmc
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: bletchley mori s8036 dl360poc mtjade swift e3c246d4i mtmitchell tatlin-archive-x86 ethanolx nicole tiogapass evb-ast2500 olympus-nuvoton transformers evb-ast2600 on5263m5 vegman-n110 evb-npcm750 p10bmc vegman-rx20 f0b palmetto vegman-sx20 fp5280g2 qcom-dc-scm-v1 witherspoon g220a quanta-q71l witherspoon-tacoma gbs romed8hm3 x11spi greatlakes romulus yosemitev2 gsj s2600wf zaius kudo s6q lannister s7106
Once you know the target (e.g. romulus), source the
setup script as follows:
. setup romulus
Additional details can be found in the docs repository.
The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here
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.
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.
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
First, please do a search on the internet. There's a good chance your question has already been asked.
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.
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.
Dive deeper into OpenBMC by opening the docs repository.
The Technical Steering Committee (TSC) guides the project. Members are: