| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | PowerSupplyRedundancy.interface.yaml | 4 - name: PowerSupplyRedundancyEnabled
5 type: boolean
7 - const
10 - name: RotationEnabled
11 type: boolean
14 - name: RotationAlgorithm
15 type: enum[self.Algo]
17 Rotation algorithm use for cold redundancy. 0 is BMC Specific, 1 is
18 User Specific.
19 - name: RotationRankOrder
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Key.v1_4_1.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
32 "type": "object" string
39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
41 "type": [ array
[all …]
|
| H A D | PrivilegeRegistry.v1_1_5.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
33 "type": "object" string
37 …"description": "The mapping between a resource type and the relevant privileges that accesses the …
38 …"longDescription": "This type shall describe a mapping between a resource type and the relevant pr…
[all …]
|
| H A D | KeyPolicy.v1_0_1.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
32 "type": "object" string
39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
41 "type": [ array
[all …]
|
| H A D | VCATEntry.v1_0_3.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
32 "type": "object" string
36 "description": "The available OEM-specific actions for this resource.",
37 …"longDescription": "This type shall contain the available OEM-specific actions for this resource.",
[all …]
|
| H A D | License.v1_1_4.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
32 "type": "object" string
42 … authorizes functionality to a number of devices, but not restricted to specific device instances.…
43 "Device": "The license authorizes functionality for specific device instances.",
[all …]
|
| H A D | StorageControllerMetrics.v1_0_3.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
32 "type": "object" string
37 …"longDescription": "The object shall contain the NVMe-defined 'Endurance Group Critical Warning Su…
39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| H A D | LogEntry.v1_19_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
33 "type": "object" string
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
42 "type": [ array
[all …]
|
| H A D | Event.v1_11_1.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
33 "type": "object" string
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
42 "type": [ array
[all …]
|
| H A D | Bios.v1_2_3.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
34 "description": "The available OEM-specific actions for this resource.",
35 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
38 "type": "object" string
45 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
47 "type": [ array
[all …]
|
| H A D | Connection.v1_4_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
16 "type": "string" string
28 "NonOptimized": "The resource is in an active and non-optimized state.",
35 … "NonOptimized": "This value shall indicate the resource is in an active and non-optimized state.",
41 …"longDescription": "This type shall describe the access to the associated resource in this connect…
42 "type": "string" string
47 "longDescription": "This type shall contain the available actions for this resource.",
49 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
51 "type": [ array
[all …]
|
| H A D | Assembly.v1_5_1.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
32 "type": "object" string
39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
41 "type": [ array
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/config_file/ |
| H A D | README.md | 1 # phosphor-power-sequencer Configuration File
5 - [Overview](#overview)
6 - [Data Format](#data-format)
7 - [Name](#name)
8 - [Contents](#contents)
9 - [Installation](#installation)
13 The `phosphor-power-sequencer` configuration file (config file) contains
22 general error when a pgood fault occurs. No specific rail will be identified.
31 The config file name is based on the system type that it supports.
33 A config file is normally system-specific. Each system type usually has a
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/ |
| H A D | Create.interface.yaml | 3 interface is for user to request a particular type of dump.
6 xyz.openbmc_project.Dump.Create per dump type on
7 /xyz/openbmc_project/dump/<dump type>. On multi-host or on multi-BMC systems
9 /xyz/openbmc_project/dump/<dump type><instance-id>.
12 - name: CreateDump
16 - name: AdditionalData
17 type: dict[string, variant[string,uint64]]
20 this case should be an implementation specific enum defined for
21 the specific type of dump either in xyz or in a domain. The
23 enum-format string is required to come from a parallel class
[all …]
|
| /openbmc/pldm/docs/ |
| H A D | pdr_implementation.md | 4 they can vary across platforms and systems. For this reason, platform specific
5 PDR information is encoded in platform specific JSON files. JSON files must be
6 named based on the PDR type number. For example a state effecter PDR JSON file
8 additional processing (apart from PDR creation) for specific PDR types, for eg
9 mapping an effecter id to a D-Bus object.
12 PDR repository. Platform specific PDR modifications would likely just result in
13 JSON updates. New PDR type support would require JSON updates as well as PDR
14 generation code. The PDR generator is a map of PDR Type -> C++ lambda to create
15 PDR entries for that type based on the JSON, and to update the central PDR repo.
|
| H A D | bios_implementation.md | 11 are structured within JSON files. Each attribute is defined by its name, type,
12 and type-specific metadata. PLDM parses
15 [Base BIOS Table](https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_…
16 hosted by [BIOS Config Manager](https://github.com/openbmc/bios-settings-mgr).
18 [DesignDoc](https://github.com/openbmc/docs/blob/master/designs/remote-bios-configuration.md).
23 [Base BIOS Table](https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_…
34 is provided in bios_attr.json file which contains attributes of type enum,
88 …cifies the character encoding format, which can be ASCII, Hex, UTF-8, UTF-16LE, or UTF-16BE. Curre…
101 system-specific BIOS attributes is crucial. To achieve this, BIOS JSON files are
102 organized under folders named after the system type. System type information is
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | IPMI.interface.yaml | 6 type followed by type-specific information. The type-specific information
8 adding the SEL record), sensor number, event direction and event-specific
9 data for system type events; or timestamp and OEM data for OEM type events.
11 The interface allows adding system or OEM type events. For system type
12 events it requires a generator ID (0x20 for BMC), sensor D-Bus path, event
13 direction (assertion or de-assertion), and event specific data. For OEM type
14 events, it requires the record type and OEM data.
19 - name: IpmiSelAdd
21 Log a system event record type SEL entry.
23 - name: Message
[all …]
|
| /openbmc/openbmc/meta-nuvoton/recipes-nuvoton/program-edid/program-edid/ |
| H A D | edid.json | 8 "DPM active-off supported": true,
12 "Display color type": "RGB 4:4:4 + YCrCb 4:4:4",
19 "Video input type": "Digital",
69 "Sync type": {
70 "Horizontal sync (outside of V-sync)": "Positive",
71 "Type": "Digital Separate Sync", string
74 "Type": "Detailed Timing Descriptor" string
104 "Sync type": {
105 "Horizontal sync (outside of V-sync)": "Positive",
106 "Type": "Digital Separate Sync", string
[all …]
|
| /openbmc/libcper/specification/json/sections/ |
| H A D | cper-vtd-dmar.json | 2 "$schema": "https://json-schema.org/draft/2020-12/schema",
3 "type": "object", string
4 "description": "VT for Directed I/O specific DMAr Error Section",
27 "type": "integer", string
28 "description": "Value of version register as defined in VT-d architecture"
31 "type": "integer", string
32 … "description": "Value of revision field in VT-d specific DMA remapping reporting structure"
35 "type": "integer", string
36 … "description": "Value of OEM ID field in VT-d specific DMA remapping reporting structure"
39 "type": "integer", string
[all …]
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 237.out | 3 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "file", "filen…
5 {"execute": "job-dismiss", "arguments": {"id": "job0"}}
8 {"execute": "blockdev-add", "arguments": {"driver": "file", "filename": "TEST_DIR/PID-t.vmdk", "nod…
10 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "vmdk", "file"…
12 {"execute": "job-dismiss", "arguments": {"id": "job0"}}
19 Format specific information:
22 create type: monolithicSparse
30 === Successful image creation (inline blockdev-add, explicit defaults) ===
32 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "file", "filen…
34 {"execute": "job-dismiss", "arguments": {"id": "job0"}}
[all …]
|
| /openbmc/libpldm/include/libpldm/oem/ibm/ |
| H A D | file_io.h | 1 /* SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later */
13 /** @brief PLDM Commands in IBM OEM type
31 /** @brief PLDM Command specific codes
127 * @param[in] msg - Pointer to PLDM request message
128 * @param[in] payload_length - Length of request payload
129 * @param[out] file_handle - A handle to the file
130 * @param[out] offset - Offset to the file at which the read should begin
131 * @param[out] length - Number of bytes to be read
132 * @param[out] address - Memory address where the file content has to be
143 * @param[in] instance_id - Message's instance id
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | LogEntry.v1_19_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
33 "type": "object" string
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
42 "type": [ array
[all …]
|
| H A D | Event.v1_11_1.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
33 "type": "object" string
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
42 "type": [ array
[all …]
|
| H A D | Bios.v1_2_3.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
34 "description": "The available OEM-specific actions for this resource.",
35 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
38 "type": "object" string
45 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
47 "type": [ array
[all …]
|
| /openbmc/docs/designs/management-console/ |
| H A D | service-discovery.md | 7 Created: 2019-07-12
11 1. <https://www.engineersgarage.com/Articles/IoT-Service-Discovery-Protocols>
14 4. <https://github.com/lathiat/avahi/blob/master/avahi-daemon/example.service>
16 Apple’s Bonjour uses mDNS and DNS-SD. Linux’s Avahi uses IPv4LL, mDNS, and
17 DNS-SD. Linux’s systemd uses resolve hostnames on a network via DNS, mDNS, and
24 wants to discover the vendor-specific server.
26 eg: Management console wants to discover the low-end server of manufacturer XYZ.
32 mDNS/DNS-SD protocol suite. BMC publishes the hostname and interface details to
35 The services that are being published by Avahi have various fields like -
36 service name, type, port, hostname, address, port, and a text record. To solve
[all …]
|