| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Community-Spec-1.0 | 1 Community Specification License 1.0
19 exercise copyright rights in the Specification, including the rights to
20 submit the Specification to another standards organization.
27 Attribution is not required for implementations of the Specification.
39 Contributor’s Contributions and 2) to the Draft Specification that
41 Licensee’s Implementation of the Draft Specification, except for those
47 license to its Necessary Claims included the Approved Specification
49 Specification, except for those patent claims excluded by Contributor
72 Specification’s repository’s Notices.md file by the Implementer’s
74 individual and system identifier, and Specification version.
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Protocol.json | 94 … shall indicate conformance to the Intel Advanced Host Controller Interface (AHCI) Specification.",
95 … "CXL": "This value shall indicate conformance to the Compute Express Link Specification.",
96 …l indicate conformance to the Digital Display Working Group DVI-A, DVI-D, or DVI-I Specification.",
97 … "DisplayPort": "This value shall indicate conformance to the VESA DisplayPort Specification.",
98 … "Ethernet": "This value shall indicate conformance to the IEEE 802.3 Ethernet specification.",
99 …all indicate conformance to the T11 Fibre Channel Physical and Signaling Interface Specification.",
101 "FCoE": "This value shall indicate conformance to the T11 FC-BB-5 Specification.",
104 "GenZ": "This value shall indicate conformance to the Gen-Z Core Specification.",
105 … "HDMI": "This value shall indicate conformance to the HDMI Forum HDMI Specification.",
108 … "I2C": "This value shall indicate conformance to the NXP Semiconductors I2C-bus Specification.",
[all …]
|
| H A D | KeyPolicy.v1_0_1.json | 119 …for properties that this object contains shall conform to the Redfish Specification-described requ…
270 … by the 'Mandatory and Recommended Cipher Suites' clause in the NVMe TCP Transport Specification.",
271 …d by the 'Mandatory and Recommended Cipher Suites' clause in the NVMe TCP Transport Specification."
293 …ned by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base Specification.",
294 …ned by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base Specification.",
295 …ned by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base Specification.",
296 …ned by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base Specification.",
297 …ined by the 'DH-HMAC-CHAP Diffie-Hellman group identifiers' figure in the NVMe Base Specification."
315 …as defined by the 'DH-HMAC-CHAP hash function identifiers' figure in the NVMe Base Specification.",
316 …as defined by the 'DH-HMAC-CHAP hash function identifiers' figure in the NVMe Base Specification.",
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Protocol.json | 94 … shall indicate conformance to the Intel Advanced Host Controller Interface (AHCI) Specification.",
95 … "CXL": "This value shall indicate conformance to the Compute Express Link Specification.",
96 …l indicate conformance to the Digital Display Working Group DVI-A, DVI-D, or DVI-I Specification.",
97 … "DisplayPort": "This value shall indicate conformance to the VESA DisplayPort Specification.",
98 … "Ethernet": "This value shall indicate conformance to the IEEE 802.3 Ethernet specification.",
99 …all indicate conformance to the T11 Fibre Channel Physical and Signaling Interface Specification.",
101 "FCoE": "This value shall indicate conformance to the T11 FC-BB-5 Specification.",
104 "GenZ": "This value shall indicate conformance to the Gen-Z Core Specification.",
105 … "HDMI": "This value shall indicate conformance to the HDMI Forum HDMI Specification.",
108 … "I2C": "This value shall indicate conformance to the NXP Semiconductors I2C-bus Specification.",
[all …]
|
| /openbmc/linux/drivers/staging/greybus/ |
| H A D | Kconfig | 9 Greybus Audio Class specification.
30 Greybus Bootrom Class specification.
40 Greybus Camera Class specification.
50 Greybus Firmware Download Class specification.
60 Greybus HID Class specification.
70 Greybus LED Class specification.
79 Greybus Debug Log Class specification.
88 Greybus Debug Log Class specification.
98 Greybus Powersupply Class specification.
107 Greybus Raw Class specification.
[all …]
|
| /openbmc/libcper/ |
| H A D | .gitignore | 15 specification/document/*.out
16 specification/document/*.pdf
17 specification/document/*.toc
18 specification/document/*.lot
19 specification/document/*.log
20 specification/document/*.fls
21 specification/document/*.fdb_*
22 specification/document/*.*gz
23 specification/document/*aux
|
| H A D | README.md | 4 described in UEFI Specification Appendix N) in a human-readable JSON format, in
54 ## Specification section in CPER JSON Representation & Conversion Library
56 The specification for this project's CPER-JSON format can be found in
57 `specification/`, defined in both JSON Schema format and also as a LaTeX
58 document. Specification for the CPER binary format can be found in
59 [UEFI Specification Appendix N](https://uefi.org/sites/default/files/resources/UEFI_Spec_2_9_2021_0…
|
| /openbmc/linux/drivers/char/tpm/ |
| H A D | Kconfig | 14 implements the Trusted Computing Group's specification,
18 userspace enablement piece of the specification, can be
48 tristate "TPM Interface Specification 1.2 Interface / TPM 2.0 FIFO Interface"
53 TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO
54 specification (TPM2.0) say Yes and it will be accessible from
59 tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (SPI)"
65 TCG TIS 1.3 TPM specification (TPM1.2) or the TCG PTP FIFO
66 specification (TPM2.0) say Yes and it will be accessible from
78 tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (I2C - generic)"
84 (I2C interface) specification and connected to an I2C bus master,
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/riscv/ |
| H A D | extensions.yaml | 41 Due to revisions of the ISA specification, some deviations
47 While the isa strings in ISA specification are case
57 version of the unprivileged ISA specification.
72 version of the unprivileged ISA specification.
76 20191213 version of the unprivileged specification.
82 specification.
87 20191213 version of the unprivileged ISA specification.
93 specification.
99 specification.
105 specification.
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-devtools/ruby/ruby/ |
| H A D | 0005-Mark-Gemspec-reproducible-change-fixing-784225-too.patch | 11 lib/rubygems/specification.rb | 4 +++-
14 diff --git a/lib/rubygems/specification.rb b/lib/rubygems/specification.rb
16 --- a/lib/rubygems/specification.rb
17 +++ b/lib/rubygems/specification.rb
18 @@ -1707,7 +1707,9 @@ class Gem::Specification < Gem::BasicSpecification
20 "invalid date format in specification: #{date.inspect}")
|
| /openbmc/libcper/cli-app/ |
| H A D | cper-convert.c | 46 } else if (strcmp(argv[i], "--specification") == 0 && in main()
48 //Specification file. in main()
53 //Invalidates specification file. in main()
144 //Validate the JSON against specification, unless otherwise specified. in json_to_cper()
148 //Is there a specification file path? in json_to_cper()
152 …//Make the specification path the assumed default (application directory + specification/cper-json… in json_to_cper()
157 "/specification/cper-json.json"); in json_to_cper()
165 //Attempt to verify with the the specification. in json_to_cper()
170 //Free specification path (if necessary). in json_to_cper()
213 …printf("\n:: to-cper cper.json --out file.name [--no-validate] [--debug] [--specification some/spe… in print_help()
[all …]
|
| /openbmc/ipmitool/src/plugins/lanplus/ |
| H A D | README.lanplus | 2 BMC. In some places, the IPMIv2 specification is either unclear or
3 inconsistent, and interpretations of the intent of the specification had to
11 specification states that K1 and K2 are generated with an HMAC algorithm,
17 * The IPMIv2 specification describes a key, Kg, that is the "BMC key".
21 per the specification section 13.33. A user can obtain the status of Kg by
27 * The specification is unclear as to which key is used for HMAC based
35 integrity and confidentiality algorithms defined in this specification,
46 command specification, as it mentions the ability to query for 16/20 byte
50 * The IPMIv2 specification describes a type of login called a "role only
59 specification, there are two fields that are rather ambiguous in meaning.
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | Protocol_v1.xml | 32 …on" String="This value shall indicate conformance to the PCI-SIG PCI Express Base Specification."/>
36 …shall indicate conformance to the Intel Advanced Host Controller Interface (AHCI) Specification."/>
40 …terface (UHCI) Specification, Enhanced Host Controller Interface Specification, or the Extensible …
44 …tion" String="This value shall indicate conformance to the T10 SAS Protocol Layer Specification."/>
48 …hall indicate conformance to the Serial ATA International Organization Serial ATA Specification."/>
52 …lue shall indicate conformance to the USB Implementers Forum Universal Serial Bus Specification."/>
56 …e shall indicate conformance to the Non-Volatile Memory Host Controller Interface Specification."/>
60 …ll indicate conformance to the T11 Fibre Channel Physical and Signaling Interface Specification."/>
64 …ndicate conformance to the IETF Internet Small Computer Systems Interface (iSCSI) Specification."/>
68 …LongDescription" String="This value shall indicate conformance to the T11 FC-BB-5 Specification."/>
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | Protocol_v1.xml | 32 …on" String="This value shall indicate conformance to the PCI-SIG PCI Express Base Specification."/>
36 …shall indicate conformance to the Intel Advanced Host Controller Interface (AHCI) Specification."/>
40 …terface (UHCI) Specification, Enhanced Host Controller Interface Specification, or the Extensible …
44 …tion" String="This value shall indicate conformance to the T10 SAS Protocol Layer Specification."/>
48 …hall indicate conformance to the Serial ATA International Organization Serial ATA Specification."/>
52 …lue shall indicate conformance to the USB Implementers Forum Universal Serial Bus Specification."/>
56 …e shall indicate conformance to the Non-Volatile Memory Host Controller Interface Specification."/>
60 …ll indicate conformance to the T11 Fibre Channel Physical and Signaling Interface Specification."/>
64 …ndicate conformance to the IETF Internet Small Computer Systems Interface (iSCSI) Specification."/>
68 …LongDescription" String="This value shall indicate conformance to the T11 FC-BB-5 Specification."/>
[all …]
|
| /openbmc/linux/drivers/acpi/acpica/ |
| H A D | utstrtoul64.c | 24 * 2) Runtime "Explicit conversion" as defined in the ACPI specification.
25 * 3) Runtime "Implicit conversion" as defined in the ACPI specification.
50 * interface. According the ACPI specification, there is no ACPI runtime
162 * an "implicit conversion" by the ACPI specification. Used by
171 * Octal strings are not supported, as per the ACPI specification.
177 * Conversion rules as extracted from the ACPI specification:
182 * 1) According to the ACPI specification, a "0x" prefix is not allowed.
201 * interpreter - All runtime implicit conversions, as per ACPI specification
217 * Per the ACPI specification, only hexadecimal is supported for in acpi_ut_implicit_strtoul64()
228 * Ignore overflow as per the ACPI specification. This is implemented by in acpi_ut_implicit_strtoul64()
[all …]
|
| /openbmc/u-boot/drivers/tpm/ |
| H A D | Kconfig | 33 to the device using the standard TPM Interface Specification (TIS)
42 to the device using the standard TPM Interface Specification (TIS)
66 to the device using the standard TPM Interface Specification (TIS)
74 TCG Main Specification 1.2. OIAP-authorised versions of the commands
84 to the device using the standard TPM Interface Specification (TIS)
93 to the device using the standard TPM Interface Specification (TIS)
145 to the device using the standard TPM Interface Specification (TIS)
154 to the device using the standard TPM Interface Specification (TIS)
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp-standards.svg | 71 …:11.28888893px;line-height:125%;font-family:sans-serif;-inkscape-font-specification:'sans-serif, N…
79 …:normal;font-size:11.28888893px;font-family:sans-serif;-inkscape-font-specification:'sans-serif, N…
84 …:11.28888893px;line-height:125%;font-family:sans-serif;-inkscape-font-specification:'sans-serif, N…
86 …:normal;font-size:11.28888893px;font-family:sans-serif;-inkscape-font-specification:'sans-serif, N…
104 …:11.28888893px;line-height:125%;font-family:sans-serif;-inkscape-font-specification:'sans-serif, N…
106 …:normal;font-size:11.28888893px;font-family:sans-serif;-inkscape-font-specification:'sans-serif, N…
124 …:11.28888893px;line-height:125%;font-family:sans-serif;-inkscape-font-specification:'sans-serif, N…
126 …:normal;font-size:11.28888893px;font-family:sans-serif;-inkscape-font-specification:'sans-serif, N…
131 …h:normal;font-size:7.05555534px;font-family:sans-serif;-inkscape-font-specification:'sans-serif, N…
147 …:11.28888893px;line-height:125%;font-family:sans-serif;-inkscape-font-specification:'sans-serif, N…
[all …]
|
| /openbmc/u-boot/lib/efi_loader/ |
| H A D | efi_device_path_utilities.c | 21 * See the Unified Extensible Firmware Interface (UEFI) specification
49 * See the Unified Extensible Firmware Interface (UEFI) specification
68 * See the Unified Extensible Firmware Interface (UEFI) specification
89 * See the Unified Extensible Firmware Interface (UEFI) specification
110 * See the Unified Extensible Firmware Interface (UEFI) specification
132 * See the Unified Extensible Firmware Interface (UEFI) specification
154 * See the Unified Extensible Firmware Interface (UEFI) specification
174 * See the Unified Extensible Firmware Interface (UEFI) specification
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/licenses/ |
| H A D | AOM-Patent-License-1.0 | 45 1.4. Disclaimers. The Reference Implementation and Specification are provided
47 otherwise using the Reference Implementation or Specification is assumed
68 non-optional portions of the Specification.
91 Media working group that developed the Specification.
98 as if the Specification was a W3C Recommendation; or (ii) are infringed
105 2.12. Specification. "Specification" means the specification designated by
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-i3c | 22 the I3C specification for a detailed description of what each
52 length, etc. See the I3C specification for more details.
62 specification for more details.
74 See the I3C specification for more details.
85 See the I3C specification for more details about these HDR
112 length, etc. See the I3C specification for more details.
120 specification for more details.
130 See the I3C specification for more details.
140 See the I3C specification for more details about these HDR
|
| /openbmc/linux/Documentation/RCU/Design/Requirements/ |
| H A D | ReadersPartitionGP1.svg | 119 …00000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"><fl…
134 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
166 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
177 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
188 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
199 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
210 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
221 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
232 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
243 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
[all …]
|
| H A D | GPpartitionReaders1.svg | 91 …00000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"><fl…
106 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
138 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
149 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
160 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
171 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
182 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
193 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
204 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
215 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
[all …]
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | v4l2-controls.h | 1374 * sequence parameter set syntax as specified by the H264 specification.
1376 * @profile_idc: see H264 specification.
1377 * @constraint_set_flags: see H264 specification.
1378 * @level_idc: see H264 specification.
1379 * @seq_parameter_set_id: see H264 specification.
1380 * @chroma_format_idc: see H264 specification.
1381 * @bit_depth_luma_minus8: see H264 specification.
1382 * @bit_depth_chroma_minus8: see H264 specification.
1383 * @log2_max_frame_num_minus4: see H264 specification.
1384 * @pic_order_cnt_type: see H264 specification.
[all …]
|
| /openbmc/linux/drivers/cxl/ |
| H A D | Kconfig | 23 The CXL specification defines a "CXL memory device" sub-class in the
32 Type 3 CXL Device in the CXL 2.0 specification for more details.
43 number for each specification defined opcode. At any given point in
44 time the number of opcodes that the specification defines and a device
46 numbers. The mismatch is either by omission, specification is too new,
63 specification, and CXL Fixed Memory Window Structures (CEDT.CFMWS)
96 specification for a detailed description of HDM.
|
| /openbmc/qemu/target/sparc/ |
| H A D | cpu-param.h | 32 * Architecture specification.
34 * The RMO memory model described in the SPARC V9 specification was
40 * D.5 Specification of Partial Store Order (PSO)
43 * D.6 Specification of Total Store Order (TSO)
|
![[all …]](/more/openbmc/docs/designs/mctp/mctp-standards.svg?full=Specification){kind=link}
![[all …]](/more/openbmc/linux/Documentation/RCU/Design/Requirements/ReadersPartitionGP1.svg?full=Specification){kind=link}
![[all …]](/more/openbmc/linux/Documentation/RCU/Design/Requirements/GPpartitionReaders1.svg?full=Specification){kind=link}