| commit | 8e88518a37ad9cf30e65a38a4deb4999a4918eef | [log] [tgz] |
|---|---|---|
| author | gBMC Team <gbmc-core@google.com> | Mon Oct 13 12:41:45 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 13 12:42:32 2025 -0700 |
| tree | 8c0ae7fe24cf0e544ff5f699f0f344fad07b3992 | |
| parent | e6a9c59295d0592fd369d362b96e3de3238ea407 [diff] |
gbmcweb: tlbmc: Add BOARD_INFO_AM3/4 to ProbeV2 fields
Adds support for BOARD_INFO_AM3 and BOARD_INFO_AM4 FRU fields. Mandolin
Beach uses BOARD_INFO_AM3 for POL vendor and BOARD_INFO_AM4 for the
revision ID (PEVT, EVT, etc) so tlbmc ProbeV2 needs to support it.
Tested:
- Successfully built and flashed to MB PTV unit with the following
yusaku probe:
```
"ProbeV2": {
"IpmiFru": [
{
"BOARD_PRODUCT_NAME": "^Mandolin Beach$",
"BOARD_INFO_AM3": "^IFX$",
"BOARD_INFO_AM4": "^PTV$"
},
{
"BOARD_PRODUCT_NAME": "^Mandolin Beach$",
"BOARD_INFO_AM3": "^IFX$",
"BOARD_INFO_AM4": "^PEVT[0-9]*$"
},
{
"BOARD_PRODUCT_NAME": "^Mandolin Beach$",
"BOARD_INFO_AM3": "^IFX$",
"BOARD_INFO_AM4": "^EVT[0-9]*$"
},
{
"BOARD_PRODUCT_NAME": "^Mandolin Beach$",
"BOARD_INFO_AM3": "^IFX$",
"BOARD_INFO_AM4": "^DVT[0-9]*$"
},
{
"BOARD_PRODUCT_NAME": "^Mandolin Beach$",
"BOARD_INFO_AM3": "^IFX$",
"BOARD_INFO_AM4": "^PVT[0-9]*$"
},
{
"BOARD_PRODUCT_NAME": "^Mandolin Beach$",
"BOARD_INFO_AM3": "^IFX$",
"BOARD_INFO_AM4": "^GA[0-9]*$"
}
]
},
```
- Verified that tlbmc is enabled in bmcweb journal
- Verified that sensors exposed through tlbmc are seen in
redfish/tlbmc/AllSensors
Note that the content of this CL was provided by Foxconn, in this gerrit
review:
- 54377: gbmcweb: tlbmc: Add BOARD_INFO_AM3/4 to ProbeV2 fields | https://gbmc-review.git.corp.google.com/c/gbmcweb/+/54377
PiperOrigin-RevId: 818786515
Change-Id: I26938fedfa1fc39b79e9c7d88dd469889e8805cd
This project is Google's version of BMCWeb.
See Readme Google for Google added features. The following is the original README of OpenBMC/BMCWeb.
==============================================================================
This component attempts to be a “do everything” embedded webserver for OpenBMC.
The webserver implements a few distinct interfaces:
bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL.
Bmcweb supports multiple authentication protocols:
Each of these types of authentication is able to be enabled or disabled both via runtime policy changes (through the relevant Redfish APIs) or via configure time options. All authentication mechanisms supporting username/password are routed to libpam, to allow for customization in authentication implementations.
All authorization in bmcweb is determined at routing time, and per route, and conform to the Redfish PrivilegeRegistry.
*Note: Non-Redfish functions are mapped to the closest equivalent Redfish privilege level.
bmcweb is configured per the meson build files. Available options are documented in meson_options.txt
meson builddir ninja -C builddir
If any of the dependencies are not found on the host system during configuration, meson will automatically download them via its wrap dependencies mentioned in bmcweb/subprojects.
bmcweb relies on some on-system data for storage of persistent data that is internal to the process. Details on the exact data stored and when it is read/written can seen from the persistent_data namespace.
When SSL support is enabled and a usable certificate is not found, bmcweb will generate a self-signed a certificate before launching the server. Please see the bmcweb source code for details on the parameters this certificate is built with.
bmcweb is capable of aggregating resources from satellite BMCs. Refer to AGGREGATION.md for more information on how to enable and use this feature.