Provide an OEM method to get Oem data from firmware into
the normalized form, and use that to hook the SMM
firmware information.
Change-Id: I7028c510afebf103fb6e0aaabdf085de3472eef2
IB adapters may be modeled with 'None' Ethernet elements.
Handle this and also check for InfiniBand instead.
Change-Id: I80b6769b3bb4c5f478cb48b261f5666dfd6a97e0
Fixup more sensor scenarios.
Give OEM a mechanism to opt out of generic sensors. If, for example, the
platform is unreasonably slow at servicing the sensors.
Change-Id: Ie8668ac219fc5d90f95dd980ffecd73a09ddd0cd
Some implementations forcibly detach on token expiry,
switch to basic authentication to persist remote media mount.
Change-Id: I39231e257156c48a8b4f21ea73aa8fcdcfe879c2
Map the IPMI API to redfish behavior for generic redfish
manipulation.
Also, have the SMM3 handler explicitly indicate that system config
does not apply.
Change-Id: I1bbb16507b6e76bb460217c63d326c8e45155d89
For identify, there are implementations with
partially broken system urls that are not good for general
operation, but are still the only target for identify.
Change-Id: I82f77e667974a57ee857082e6cbc98b78b818ccd
If an endpoint has no system, use chassis for data.
Further, for SMM3, do some fixup on 'Model' versus 'SKU'.
Change-Id: Ibf8d72381057d43f9ad59469078fd4899330c74f
When generic sensors are available, use them over the older,
more limited CPU and thermal data.
Also, if an endpoint has no viable system, allow sensors to
dig into chassis anyway, for enclosure type endpoints.
Change-Id: Ifd575797381801c60cff6e4dc2053f4e25002a15
SMMv3 does something a bit peculiar, and to accomodate it,
provide a way for the OEM code to describe additional
log services not attached to the BMC resource.
Change-Id: I01a6ba50ac462840749eeb6b07400b66930beb1d
The SMM3 for the 2025 generation of DWC represents
a 13U chassis and vertical geometry.
Make provisions to support a redfish endpoint with no
or malfunctioning 'system' for enclosure-only redfish.
Change-Id: I0625e4587da3b76343cf796c45a9e79f240f394c
Similar to XCC2, we must get at the underlying uxz file
if we want to steer it.
We also must use the multipart form data to pass json with right
Content-Type, add a mechanism to auto-json a dict to acheive this.
Change-Id: If204d7a05399e39cd43ffd7622559ab10d906b47
XCC3 has some OEM settings managed in a redfish
settings registry sort of way. Refactor
to pull out generic registry handling and use it
with XCC3 settings as well as UEFI.
Manifest 'XCC' settings with 'XCC.' prefix, imitating the 'IMM.' of
the past. Since OData forbids '.', this means XCC. cannot
conflict with hypothetical BIOS names that may conflict.
Change-Id: Idb9e5ecffdc0d27f20ae070acdc3cd78658a0955
There is yet another flavor of MAC address organization.
So make sure we provide chances to hit it at least three of
the various ways redfish may choose to manifest mac addresses.
There are other paths to the data as well, but hopefully an
implementation at least implements one of the three.
Change-Id: Iaba947e2e16f14b6e7a94018beac046efd73bc25
