| /openbmc/bmcweb/ |
| H A D | OEM_SCHEMAS.md | 1 # Redfish OEM Schemas
3 The Redfish specification allows for OEM resources and properties to be
4 implemented by OEMs. bmcweb does not expose a stable API for adding OEM
8 ## OEM Compatibility and authority
11 organization is responsible for maintaining that company's OEM namespace. They
17 Because of that, OEM properties in an open-source project pose many problems
28 In the experience of the project, OEM resources trend toward a lower level of
35 If a given feature eventually becomes standardized, OpenBMC OEM endpoints now
38 be completed before merging the OEM code to master.
47 In the current implementation, OEM schemas for all namespaces are shipped on all
[all …]
|
| /openbmc/phosphor-host-ipmid/docs/ |
| H A D | oem-extension-numbering.md | 1 # Sketch of OpenBMC OEM message formats
3 This document describes OEM Requests to be supported using the OpenBMC OEM
8 - Briefly recap OEM Extension layout as described in IPMI Specification.
9 - Enumerate Command codes allocated for use with the OpenBMC OEM Number.
13 ## OEM Extensions, Block Transfer Transport Example
15 This table and the next briefly recap OEM Extension messages as described in the
20 ### OEM Request
27 | 1 | 2:7 | NetFn | 0x2E | OEM Request |
31 | 4 ~ 6 | | OEN | 49871 | OEM Enterprise Number |
39 - Serialize numbers larger than 1 byte LSB first - e.g., represent OEM
[all …]
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | processor.hpp | 20 OEM, enumerator
53 OEM, enumerator
71 OEM, enumerator
93 OEM, enumerator
106 {ProcessorType::OEM, "OEM"},
139 {ProcessorMemoryType::OEM, "OEM"},
157 {SystemInterfaceType::OEM, "OEM"},
179 {ThrottleCause::OEM, "OEM"},
|
| H A D | log_service.hpp | 22 OEM, enumerator
72 OEM, enumerator
82 OEM, enumerator
95 OEM, enumerator
118 {LogEntryTypes::OEM, "OEM"},
168 {LogDiagnosticDataTypes::OEM, "OEM"},
178 {LogPurpose::OEM, "OEM"},
191 {TransferProtocolType::OEM, "OEM"},
|
| H A D | account_service.hpp | 19 OEM, enumerator
35 OEM, enumerator
45 OEM, enumerator
86 {MFABypassType::OEM, "OEM"},
102 {AccountProviderTypes::OEM, "OEM"},
112 {AuthenticationTypes::OEM, "OEM"},
|
| H A D | connection_method.hpp | 17 OEM, enumerator
23 OEM, enumerator
33 {ConnectionMethodType::OEM, "OEM"},
39 {TunnelingProtocolType::OEM, "OEM"},
|
| H A D | computer_system.hpp | 103 OEM, enumerator
112 OEM, enumerator
147 OEM, enumerator
153 OEM, enumerator
175 OEM, enumerator
310 {WatchdogWarningActions::OEM, "OEM"},
319 {WatchdogTimeoutActions::OEM, "OEM"},
354 {BootProgressTypes::OEM, "OEM"},
360 {GraphicalConnectTypesSupported::OEM, "OEM"},
382 {PowerMode::OEM, "OEM"},
|
| H A D | external_account_provider.hpp | 15 OEM, enumerator
25 OEM, enumerator
48 {AccountProviderTypes::OEM, "OEM"},
58 {AuthenticationTypes::OEM, "OEM"},
|
| H A D | event_destination.hpp | 28 OEM, enumerator
38 OEM, enumerator
129 {EventDestinationProtocol::OEM, "OEM"},
139 {SubscriptionType::OEM, "OEM"},
|
| H A D | resolution_step.hpp | 19 OEM, enumerator
31 {ResolutionType::OEM, "OEM"},
|
| H A D | acceleration_function.hpp | 19 OEM, enumerator
31 {AccelerationFunctionType::OEM, "OEM"},
|
| H A D | software_inventory.hpp | 14 OEM, enumerator
28 {VersionScheme::OEM, "OEM"},
|
| H A D | license_service.hpp | 19 OEM, enumerator
32 {TransferProtocolType::OEM, "OEM"},
|
| H A D | outbound_connection.hpp | 22 OEM, enumerator
37 {AuthenticationType::OEM, "OEM"},
|
| /openbmc/intel-ipmi-oem/ |
| H A D | ipmi-allowlist.conf | 81 0x06:0x50:0xff7f //<App>:<Get Channel OEM Payload Info>
163 0x2e:0xC0:0x7f7f //<Intel OEM>:<Enable/Disable Node Manager Policy Control>
164 0x2e:0xC1:0x7f7f //<Intel OEM>:<Set Node Manager Policy>
165 0x2e:0xC2:0xff7f //<Intel OEM>:<Get Node Manager Policy>
166 0x2e:0xC3:0x7f7f //<Intel OEM>:<Set Node Manager Policy Alert Threshold>
167 0x2e:0xC4:0xff7f //<Intel OEM>:<Get Node Manager Policy Alert Threshold>
168 0x2e:0xC5:0x7f7f //<Intel OEM>:<Set Node Manager PolicySuspend Periods>
169 0x2e:0xC6:0xff7f //<Intel OEM>:<Get Node Manager PolicySuspend Periods>
170 0x2e:0xC7:0x7f7f //<Intel OEM>:<Reset Node Manager Statistics>
171 0x2e:0xC8:0xff7f //<Intel OEM>:<Get Node Manager Statistics>
[all …]
|
| /openbmc/phosphor-pid-control/ |
| H A D | ipmi.md | 1 # OEM-IPMI Commands to talk to Phosphor-pid-control
18 OEM commands are required to use these.
20 ## IPMI OEM Command Specification
22 ### OEM Get/Set Control Mode
29 Manual mode is controlled by zone through the following OEM command:
53 ### OEM Get Failsafe Mode
|
| /openbmc/webui-vue/src/store/modules/Operations/ |
| H A D | VirtualMediaStore.js | 13 OEM: 'OEM', property in transferProtocolType
44 transferProtocolType: transferProtocolType.OEM,
70 .filter((d) => d.transferProtocolType === transferProtocolType.OEM)
78 .filter((d) => d.transferProtocolType !== transferProtocolType.OEM)
|
| /openbmc/libpldm/ |
| H A D | README.md | 190 ## OEM/vendor-specific functions
192 libpldm accepts support for OEM or vendor-specific extensions. To add support
193 for an OEM's extensions:
195 1. Document the wire format for all OEM messages under `docs/oem/${OEM_NAME}/`
197 2. Add public OEM API declarations and definitions under
201 3. Implement the public OEM APIs under `src/oem/${OEM_NAME}/`
203 4. Implement the OEM API tests under `tests/oem/${OEM_NAME}/`
205 The `${OEM_NAME}` folder must be created with the name of the OEM/vendor in
208 Finally, the OEM name must be added to the list of choices for the `oem` meson
210 integration of the OEM extensions.
|
| /openbmc/openbmc/meta-quanta/meta-gbs/recipes-phosphor/ipmi/phosphor-ipmi-host/ |
| H A D | gbs-ipmid-whitelist.conf | 75 0x2E:0x02 //<Google OEM>:<I2C via Proxy Adapter>
76 0x2E:0x04 //<Google OEM>:<Fan Manual Control Mode>
77 0x2E:0x30 //<Google OEM>:<Ethernet Statistics>
78 0x2E:0x32 //<Google OEM>:<Sys Commands>
79 0x2E:0x80 //<Google OEM>:<Blob Commands>
|
| /openbmc/openbmc/meta-google/ |
| H A D | README | 53 * google-ipmi-sys: OEM IPMI Handler for providing specific information to the host.
54 * phosphor-ipmi-blobs: OEM IPMI Blobs Handler for providing the framework for specific blob handler…
55 * phosphor-ipmi-ethstats: OEM IPMI Handler for reporting ethernet device statistics from the BMCs e…
56 * phosphor-ipmi-flash: OEM IPMI Handler for controlling in-band firmware updates.
|
| /openbmc/libcper/docs/ |
| H A D | GeneratorExtensions.md | 1 # Extending `cper-generator` With OEM Sections
3 Much like `cper-parse`, `cper-generator` supports the addition of arbitrary OEM
4 sections as extensions. This document details how an OEM section generator could
12 sake of example, we will create a generator for a fake OEM section
46 OEM extension to `cper-parse`, so if you've already done this, you do not need
|
| /openbmc/docs/designs/ |
| H A D | redfish-authorization.md | 26 `ConfigureManager`, etc). A service may define custom OEM roles (read-only). A
47 **Note**, in the Redfish spec, OEM roles can be added via POST to the
150 own OEM roles and privileges if "the standard privilege is overly broad".
163 1. Clients shall be able to add new OEM Redfish privileges without recompile
164 2. Clients shall be able to add new OEM Redfish roles and assign it with any
172 - It rejects modification of non-OEM privileges
173 - It rejects deletion of OEM Redfish roles if any user (either local or
175 - It rejects deletion of OEM Redfish privileges if any OEM Redfish role is
180 8. Default OEM roles and Redfish privileges must be selectable on a per system
214 well with OEM Redfish Roles where a Redfish role maps to a dynamic set of OEM
[all …]
|
| /openbmc/openbmc/meta-openpower/recipes-phosphor/ipmi/openpower-ipmi-oem-whitelist/ |
| H A D | openpower-ipmi-oem-whitelist-native.conf | 2 0x3A:0x5A //<OpenPower IBM OEM>:<Host IO Mapping Protocol (HIOMAP)>
3 0x3A:0xF0 //<OpenPower IBM OEM>:<Add Partial eSEL command>
|
| /openbmc/phosphor-host-ipmid/app/ |
| H A D | watchdog.cpp | 136 OEM = 0x5, enumerator
163 case IpmiTimerUse::OEM: in ipmiTimerUseToWdTimerUse()
165 return WatchdogService::TimerUse::OEM; in ipmiTimerUseToWdTimerUse()
334 case WatchdogService::TimerUse::OEM: in wdTimerUseToIpmiTimerUse()
336 return IpmiTimerUse::OEM; in wdTimerUseToIpmiTimerUse()
|
| /openbmc/openbmc/meta-openpower/recipes-phosphor/ipmi/ |
| H A D | openpower-ipmi-oem-whitelist-native.bb | 1 SUMMARY = "Whitelisted OpenBMC IPMI OEM commands"
2 DESCRIPTION = "Whitelisted OpenBMC IPMI OEM commands for OpenPOWER based systems"
|