| /openbmc/ipmitool/lib/ |
| H A D | ipmi_oem.c | 46 .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/pldm/libpldmresponder/ |
| H A D | meson.build | 45 if get_option('oem-ibm').allowed() 46 responder_headers += ['../oem/ibm/'] 48 '../oem/ibm/libpldmresponder/utils.cpp', 49 '../oem/ibm/libpldmresponder/file_io.cpp', 50 '../oem/ibm/libpldmresponder/file_table.cpp', 51 '../oem/ibm/libpldmresponder/file_io_by_type.cpp', 52 '../oem/ibm/libpldmresponder/file_io_type_pel.cpp', 53 '../oem/ibm/libpldmresponder/file_io_type_dump.cpp', 54 '../oem/ibm/libpldmresponder/file_io_type_cert.cpp', 55 '../oem/ibm/libpldmresponder/platform_oem_ibm.cpp', [all …]
|
| /openbmc/pldm/pldmtool/oem/ibm/ |
| H A D | oem_ibm_state_set.hpp | 2 #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"}, 51 {PLDM_OEM_IBM_ENTITY_REAL_SAI, "OEM IBM Real SAI"}, [all …]
|
| /openbmc/bmcweb/docs/ |
| 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/pldm/configurations/ |
| H A D | meson.build | 9 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 D | processor.hpp | 20 OEM, enumerator 31 OEM, enumerator 46 OEM, enumerator 80 OEM, enumerator 98 OEM, enumerator 120 OEM, enumerator 133 {ProcessorType::OEM, "OEM"}, 144 {ProcessorArchitecture::OEM, "OEM"}, 159 {InstructionSet::OEM, "OEM"}, 193 {ProcessorMemoryType::OEM, "OEM"}, [all …]
|
| H A D | manager.hpp | 26 Oem, enumerator 34 Oem, enumerator 40 Oem, enumerator 66 OEM, enumerator 86 {SerialConnectTypesSupported::Oem, "Oem"}, 94 {CommandConnectTypesSupported::Oem, "Oem"}, 100 {GraphicalConnectTypesSupported::Oem, "Oem"}, 126 {SecurityModeTypes::OEM, "OEM"},
|
| H A D | connection_method.hpp | 17 OEM, enumerator 25 OEM, enumerator 35 {ConnectionMethodType::OEM, "OEM"}, 43 {TunnelingProtocolType::OEM, "OEM"},
|
| H A D | log_service.hpp | 22 OEM, enumerator 72 OEM, enumerator 83 OEM, enumerator 96 OEM, enumerator 119 {LogEntryTypes::OEM, "OEM"}, 169 {LogDiagnosticDataTypes::OEM, "OEM"}, 180 {LogPurpose::OEM, "OEM"}, 193 {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 | external_account_provider.hpp | 15 OEM, enumerator 25 OEM, enumerator 48 {AccountProviderTypes::OEM, "OEM"}, 58 {AuthenticationTypes::OEM, "OEM"},
|
| /openbmc/libpldm/include/libpldm/ |
| H A D | meson.build | 26 if get_option('oem').contains('ibm') 28 'oem/ibm/entity.h', 29 'oem/ibm/file_io.h', 30 'oem/ibm/fru.h', 31 'oem/ibm/host.h', 32 'oem/ibm/platform.h', 33 'oem/ibm/state_set.h', 37 if get_option('oem').contains('meta') 38 libpldm_headers += files('oem/meta/file_io.h')
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | ConnectionMethod.v1_2_0.json | 26 "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", 161 "OEM": "OEM connection method.", string [all …]
|
| H A D | Session.v1_8_0.json | 26 "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.", 191 "Oem": { object [all …]
|
| H A D | CertificateLocations.v1_0_4.json | 26 "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… 94 "Oem": { object 95 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem", 96 "description": "The OEM extension property.", 97 …"longDescription": "This property shall contain the OEM extensions. All values for properties tha… 139 "Oem": { object 140 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem", 141 "description": "The OEM extension property.", [all …]
|
| /openbmc/phosphor-pid-control/ipmi/ |
| H A D | main_ipmi.cpp | 26 oem::Router* router = oem::mutableRouter(); in setupGlobalOemFanControl() 30 "Registering OEM:[%#08X], Cmd:[%#04X] for Manual Zone Control\n", in setupGlobalOemFanControl() 31 oem::obmcOemNumber, oem::Cmd::fanManualCmd); in setupGlobalOemFanControl() 34 oem::obmcOemNumber, oem::Cmd::fanManualCmd, in setupGlobalOemFanControl()
|
| /openbmc/pldm/docs/ |
| H A D | code_organisation.md | 21 ## OEM/vendor-specific functions 23 This will support OEM or vendor-specific functions and semantic information. 28 |---- oem 31 |---<oem based handler files> 35 <oem_name> - This folder must be created with the name of the OEM/vendor in 39 Files having the oem functionality for the libpldmresponder library should be 40 placed under the folder oem/<oem_name>/libpldmresponder. They must be adhering 47 For consistency would recommend using "oem-<oem_name>".
|
| /openbmc/libpldm/evolutions/v0.9.1/ |
| H A D | oem-ibm-header-compat.cocci | 4 +#include <libpldm/oem/ibm/file_io.h> 9 +#include <libpldm/oem/ibm/entity.h> 14 +#include <libpldm/oem/ibm/fru.h> 19 +#include <libpldm/oem/ibm/host.h> 24 +#include <libpldm/oem/ibm/platform.h> 29 +#include <libpldm/oem/ibm/state_set.h>
|
| /openbmc/openbmc-test-automation/data/ |
| H A D | pldm_variables.py | 7 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/u-boot/include/ |
| H A D | fsl_sfp.h | 45 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 */
|
| /openbmc/google-ipmi-sys/ |
| H A D | main.cpp | 30 namespace oem namespace 36 } // namespace oem 50 stderr, "Registering OEM:[{:#08X}], Cmd:[{:#04X}] for Sys Commands\n", in setupGoogleOemSysCommands() 51 oem::googOemNumber, oem::google::sysCmd); in setupGoogleOemSysCommands() 54 ::ipmi::prioOemBase, oem::googOemNumber, oem::google::sysCmd, in setupGoogleOemSysCommands()
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Session.v1_8_0.json | 26 "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.", 191 "Oem": { object [all …]
|
| H A D | CertificateLocations.v1_0_4.json | 26 "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… 94 "Oem": { object 95 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem", 96 "description": "The OEM extension property.", 97 …"longDescription": "This property shall contain the OEM extensions. All values for properties tha… 139 "Oem": { object 140 "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem", 141 "description": "The OEM extension property.", [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/phosphor-host-ipmid/include/ipmid/ |
| H A D | oemrouter.hpp | 13 namespace oem namespace 42 /// @param[in] oen - the OEM Number. 52 /// @returns pointer to OEM Router to use. 66 /// @param[in] oeg - OEM Group reference. 73 /// Given an OEN, conver to the OEM Group. 75 /// @param[in] oen - the OEM Number. 76 /// @return the OEM Group. 84 } // namespace oem
|