Home
last modified time | relevance | path

Searched full:oem (Results 1 – 25 of 1331) sorted by relevance

12345678910>>...54

/openbmc/ipmitool/lib/
H A Dipmi_oem.c46 .desc = "Supermicro IPMIv1.5 BMC with OEM LAN authentication support",
63 .desc = "IBM OEM support",
72 .desc = "Kontron OEM big buffer support"
77 /* Supermicro IPMIv2 BMCs use OEM authtype */
96 /* ipmi_oem_print - print list of OEM handles
101 struct ipmi_oem_handle * oem; in ipmi_oem_print() local
103 for (oem=ipmi_oem_list; oem->name != NULL && oem->desc != NULL; oem++) { in ipmi_oem_print()
104 lprintf(LOG_NOTICE, "\t%-12s %s", oem->name, oem->desc); in ipmi_oem_print()
109 /* ipmi_oem_setup - do initial setup of OEM handle
112 * @oemtype: OEM handle name
[all …]
/openbmc/bmcweb/
H A DOEM_SCHEMAS.md1 # 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/pldm/libpldmresponder/
H A Dmeson.build42 if get_option('oem-ibm').allowed()
43 responder_headers += ['../oem/ibm/']
45 '../oem/ibm/libpldmresponder/utils.cpp',
46 '../oem/ibm/libpldmresponder/file_io.cpp',
47 '../oem/ibm/libpldmresponder/file_table.cpp',
48 '../oem/ibm/libpldmresponder/file_io_by_type.cpp',
49 '../oem/ibm/libpldmresponder/file_io_type_pel.cpp',
50 '../oem/ibm/libpldmresponder/file_io_type_dump.cpp',
51 '../oem/ibm/libpldmresponder/file_io_type_cert.cpp',
52 '../oem/ibm/libpldmresponder/platform_oem_ibm.cpp',
[all …]
/openbmc/pldm/pldmtool/oem/ibm/
H A Doem_ibm_state_set.hpp2 #include <libpldm/oem/ibm/entity.h>
3 #include <libpldm/oem/ibm/state_set.h>
9 /** @brief PLDM OEM IBM Code Update possible state set values
21 /** @brief PLDM OEM IBM Verification possible state set values
31 /** @brief PLDM OEM IBM system power state possible state set values
38 /** @brief PLDM OEM IBM boot state possible state set values
46 /** @brief Map for PLDM OEM IBM Entity Types
49 {PLDM_OEM_IBM_ENTITY_FIRMWARE_UPDATE, "OEM IBM Firmware Update"},
50 {PLDM_OEM_IBM_ENTITY_TPM, "OEM IBM Trusted Platform Module"}};
52 /** @brief Map for PLDM OEM IBM State Sets
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DConnectionMethod.v1_1_1.json26 "Oem": { object
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
85 …ier of the connection method. This property shall be present if `ConnectionMethodType` is `OEM`.",
116 "Oem": { object
117 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
118 "description": "The OEM extension property.",
119 …"longDescription": "This property shall contain the OEM extensions. All values for properties tha…
151 "OEM"
157 "OEM": "OEM connection method.", string
[all …]
H A DSession.v1_7_2.json26 "Oem": { object
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
54 "Oem": { object
55 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
56 "description": "The OEM extension property.",
57 …"longDescription": "This property shall contain the OEM extensions. All values for properties con…
71 "description": "The available OEM-specific actions for this resource.",
72 …"longDescription": "This type shall contain the available OEM-specific actions for this resource.",
183 "Oem": { object
[all …]
H A DLogEntry.v1_17_0.json26 "Oem": { object
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
65 "Oem": { object
66 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
67 "description": "The OEM extension property.",
68 …"longDescription": "This property shall contain the OEM extensions. All values for properties con…
134 "Oem": { object
135 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
136 "description": "The OEM extension property.",
[all …]
H A DExternalAccountProvider.v1_8_0.json12 "OEM",
20 "OEM": "An OEM-specific external authentication or directory service.", string
56 "Oem": { object
58 "description": "The available OEM-specific actions for this resource.",
59 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
128 "Oem": { object
129 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
130 "description": "The OEM extension property.",
131 …"longDescription": "This property shall contain the OEM extensions. All values for properties con…
167 "OEM"
[all …]
H A DPCIeSlots.v1_6_1.json26 "Oem": { object
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
36 "description": "The available OEM-specific actions for this resource.",
37 …"longDescription": "This type shall contain the available OEM-specific actions for this resource.",
74 "Oem": { object
75 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
76 "description": "The OEM extension property.",
77 …"longDescription": "This property shall contain the OEM extensions. All values for properties con…
166 "Oem": { object
[all …]
H A DSimpleStorage.v1_3_2.json26 "Oem": { object
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
90 "Oem": { object
91 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
92 "description": "The OEM extension property.",
93 …"longDescription": "This property shall contain the OEM extensions. All values for properties con…
132 "Oem": { object
133 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
134 "description": "The OEM extension property.",
[all …]
/openbmc/libpldm/include/libpldm/
H A Dmeson.build23 if get_option('oem').contains('ibm')
25 'oem/ibm/entity.h',
26 'oem/ibm/file_io.h',
27 'oem/ibm/fru.h',
28 'oem/ibm/host.h',
29 'oem/ibm/platform.h',
30 'oem/ibm/state_set.h',
34 if get_option('oem').contains('meta')
35 libpldm_headers += files('oem/meta/file_io.h')
/openbmc/pldm/configurations/
H A Dmeson.build9 if get_option('oem-ibm').disabled()
14 if get_option('oem-ibm').allowed()
15 install_subdir('../oem/ibm/configurations/fru', install_dir: package_datadir)
17 '../oem/ibm/configurations/events',
21 '../oem/ibm/configurations/bios',
25 '../oem/ibm/configurations/fru_master.json',
29 '../oem/ibm/configurations/entityMap.json',
33 '../oem/ibm/configurations/fileTable.json',
37 '../oem/ibm/configurations/host_eid',
/openbmc/bmcweb/redfish-core/include/generated/enums/
H A Dmanager.hpp23 Oem, enumerator
31 Oem, enumerator
37 Oem, enumerator
62 {SerialConnectTypesSupported::Oem, "Oem"},
70 {CommandConnectTypesSupported::Oem, "Oem"},
76 {GraphicalConnectTypesSupported::Oem, "Oem"},
H A Dprocessor.hpp18 OEM, enumerator
51 OEM, enumerator
69 OEM, enumerator
91 OEM, enumerator
104 {ProcessorType::OEM, "OEM"},
137 {ProcessorMemoryType::OEM, "OEM"},
155 {SystemInterfaceType::OEM, "OEM"},
177 {ThrottleCause::OEM, "OEM"},
H A Dlog_service.hpp20 OEM, enumerator
70 OEM, enumerator
80 OEM, enumerator
93 OEM, enumerator
116 {LogEntryTypes::OEM, "OEM"},
166 {LogDiagnosticDataTypes::OEM, "OEM"},
176 {LogPurpose::OEM, "OEM"},
189 {TransferProtocolType::OEM, "OEM"},
H A Daccount_service.hpp17 OEM, enumerator
33 OEM, enumerator
43 OEM, enumerator
84 {MFABypassType::OEM, "OEM"},
100 {AccountProviderTypes::OEM, "OEM"},
110 {AuthenticationTypes::OEM, "OEM"},
/openbmc/openbmc-test-automation/data/
H A Dpldm_variables.py7 PLDM_SUPPORTED_TYPES = ["base", "platform", "bios", "fru", "oem-ibm"]
14 PLDM_TYPE_OEM = {"VALUE": "63", "STRING": "oem-ibm"}
20 "63(oem-ibm)",
136 "32801(OEM)",
138 "24577(OEM)",
157 "OEM",
165 "24576(OEM)",
166 "60(OEM)",
168 "142(OEM)",
191 "32774(OEM)",
[all …]
/openbmc/libpldm/
H A DREADME.md183 ## OEM/vendor-specific functions
185 libpldm accepts support for OEM or vendor-specific extensions. To add support
186 for an OEM's extensions:
188 1. Document the wire format for all OEM messages under `docs/oem/${OEM_NAME}/`
190 2. Add public OEM API declarations and definitions under
191 `include/libpldm/oem/${OEM_NAME}/`, and install them to the same relative
194 3. Implement the public OEM APIs under `src/oem/${OEM_NAME}/`
196 4. Implement the OEM API tests under `tests/oem/${OEM_NAME}/`
198 The `${OEM_NAME}` folder must be created with the name of the OEM/vendor in
201 Finally, the OEM name must be added to the list of choices for the `oem` meson
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DSession.v1_7_2.json26 "Oem": { object
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
54 "Oem": { object
55 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
56 "description": "The OEM extension property.",
57 …"longDescription": "This property shall contain the OEM extensions. All values for properties con…
71 "description": "The available OEM-specific actions for this resource.",
72 …"longDescription": "This type shall contain the available OEM-specific actions for this resource.",
183 "Oem": { object
[all …]
H A DLogEntry.v1_17_0.json26 "Oem": { object
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
65 "Oem": { object
66 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
67 "description": "The OEM extension property.",
68 …"longDescription": "This property shall contain the OEM extensions. All values for properties con…
134 "Oem": { object
135 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
136 "description": "The OEM extension property.",
[all …]
H A DPCIeSlots.v1_6_1.json26 "Oem": { object
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
36 "description": "The available OEM-specific actions for this resource.",
37 …"longDescription": "This type shall contain the available OEM-specific actions for this resource.",
74 "Oem": { object
75 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
76 "description": "The OEM extension property.",
77 …"longDescription": "This property shall contain the OEM extensions. All values for properties con…
166 "Oem": { object
[all …]
H A DRole.v1_3_2.json26 "Oem": { object
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 "description": "The available OEM-specific actions for this resource.",
38 …"longDescription": "This type shall contain the available OEM-specific actions for this resource.",
125 …iption": "An indication of whether the role is predefined by Redfish or an OEM rather than a clien…
126 …is property shall indicate whether the role is predefined by Redfish or an OEM as contrasted with …
134 "Oem": { object
135 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem",
136 "description": "The OEM extension property.",
[all …]
/openbmc/phosphor-host-ipmid/docs/
H A Doem-extension-numbering.md1 # 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/openbmc/meta-openembedded/meta-oe/recipes-support/freeipmi/freeipmi/
H A D0001-Fix-undeclared-function-errors.patch15 ipmi-sensors/ipmi-sensors-oem-intel.c | 1 +
19 diff --git a/ipmi-sensors/ipmi-sensors-oem-intel.c b/ipmi-sensors/ipmi-sensors-oem-intel.c
21 --- a/ipmi-sensors/ipmi-sensors-oem-intel.c
22 +++ b/ipmi-sensors/ipmi-sensors-oem-intel.c
24 #include "ipmi-sensors-oem-intel-s2600jf.h"
25 #include "ipmi-sensors-oem-intel-quanta-qssc-s4r.h"
26 #include "ipmi-sensors-oem-intel-node-manager.h"
27 +#include "ipmi-sensors-oem-intel-s2600wp.h"
/openbmc/u-boot/include/
H A Dfsl_sfp.h45 u32 oem_uid; /* 0x274 OEM UID 0*/
46 u32 oem_uid_1; /* 0x278 OEM UID 1*/
47 u32 oem_uid_2; /* 0x27c OEM UID 2*/
48 u32 oem_uid_3; /* 0x280 OEM UID 3*/
49 u32 oem_uid_4; /* 0x284 OEM UID 4*/
57 u32 oem_uid; /* 0x9c OEM Unique ID */
70 u32 ospr; /* 0x40 OEM Security Policy Register */
73 u32 oem_uid; /* 0x9c OEM Unique ID */
75 u32 ovpr; /* 0xA4 OEM Validation Policy Register */

12345678910>>...54