Home
last modified time | relevance | path

Searched full:specification (Results 1 – 25 of 2079) sorted by relevance

12345678910>>...84

/openbmc/openbmc/poky/meta/files/common-licenses/
H A DCommunity-Spec-1.01 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-installed/
H A DProtocol.json96 "AHCI": "This value shall indicate conformance to the Intel Advanced Host Controller Interface (AHCI) Specification.",
97 "CXL": "This value shall indicate conformance to the Compute Express Link Specification.",
98 "DVI": "This value shall indicate conformance to the Digital Display Working Group DVI-A, DVI-D, or DVI-I Specification.",
99 "DisplayPort": "This value shall indicate conformance to the VESA DisplayPort Specification.",
100 "Ethernet": "This value shall indicate conformance to the IEEE 802.3 Ethernet specification.",
101 "FC": "This value shall indicate conformance to the T11 Fibre Channel Physical and Signaling Interface Specification.",
103 "FCoE": "This value shall indicate conformance to the T11 FC-BB-5 Specification.",
106 "GenZ": "This value shall indicate conformance to the Gen-Z Core Specification.",
107 "HDMI": "This value shall indicate conformance to the HDMI Forum HDMI Specification.",
110 "I2C": "This value shall indicate conformance to the NXP Semiconductors I2C-bus Specification
[all...]
H A DPCIeDevice.v1_19_0.json55 … "description": "An array of the CXL specification revisions supported by this device.",
66 …"longDescription": "This property shall contain an array of the CXL specification revisions that t…
80 "description": "The revision of the CXL specification in use by this device.",
81 …"longDescription": "This property shall contain the negotiated CXL specification revision in use b…
114 …"This property shall indicate whether the CXL device supports the CXL Specification-defined 'Egres…
134 …"longDescription": "This property shall indicate whether the CXL Specification-defined 'Temporary …
144 …"longDescription": "This property shall indicate whether the CXL Specification-defined 'Temporary …
153 …avor of `TemporaryThroughputReductionSupported` to align with the CXL Specification-defined FMAPI …
155 …"This property shall indicate whether the CXL device supports the CXL Specification-defined 'Throu…
187 "Type1": "This value shall indicate a CXL Specification-defined Type 1 device.",
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DProtocol.json96 … shall indicate conformance to the Intel Advanced Host Controller Interface (AHCI) Specification.",
97 … "CXL": "This value shall indicate conformance to the Compute Express Link Specification.",
98 …l indicate conformance to the Digital Display Working Group DVI-A, DVI-D, or DVI-I Specification.",
99 … "DisplayPort": "This value shall indicate conformance to the VESA DisplayPort Specification.",
100 … "Ethernet": "This value shall indicate conformance to the IEEE 802.3 Ethernet specification.",
101 …all indicate conformance to the T11 Fibre Channel Physical and Signaling Interface Specification.",
103 "FCoE": "This value shall indicate conformance to the T11 FC-BB-5 Specification.",
106 "GenZ": "This value shall indicate conformance to the Gen-Z Core Specification.",
107 … "HDMI": "This value shall indicate conformance to the HDMI Forum HDMI Specification.",
110 … "I2C": "This value shall indicate conformance to the NXP Semiconductors I2C-bus Specification.",
[all …]
H A DKeyPolicy.v1_0_1.json119 …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 …]
H A DPCIeDevice.v1_19_0.json55 … "description": "An array of the CXL specification revisions supported by this device.",
66 …"longDescription": "This property shall contain an array of the CXL specification revisions that t…
80 "description": "The revision of the CXL specification in use by this device.",
81 …"longDescription": "This property shall contain the negotiated CXL specification revision in use b…
114 …"This property shall indicate whether the CXL device supports the CXL Specification-defined 'Egres…
134 …"longDescription": "This property shall indicate whether the CXL Specification-defined 'Temporary …
144 …"longDescription": "This property shall indicate whether the CXL Specification-defined 'Temporary …
153 …avor of `TemporaryThroughputReductionSupported` to align with the CXL Specification-defined FMAPI …
155 …"This property shall indicate whether the CXL device supports the CXL Specification-defined 'Throu…
187 "Type1": "This value shall indicate a CXL Specification-defined Type 1 device.",
[all …]
/openbmc/libcper/
H A D.gitignore15 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 DREADME.md4 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/openbmc/poky/meta/recipes-devtools/ruby/ruby/
H A D0005-Mark-Gemspec-reproducible-change-fixing-784225-too.patch11 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 @@ -1711,7 +1711,9 @@ class Gem::Specification < Gem::BasicSpecification
20 "invalid date format in specification: #{date.inspect}")
H A D0006-Make-gemspecs-reproducible.patch22 @@ -14,6 +14,7 @@ Gem::Specification.new do |s|
35 Gem::Specification.new do |spec|
47 Gem::Specification.new do |s|
59 Gem::Specification.new do |spec|
72 Gem::Specification.new do |s|
/openbmc/ipmitool/src/plugins/lanplus/
H A DREADME.lanplus2 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 DProtocol_v1.xml32 …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 DProtocol_v1.xml32 …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/u-boot/drivers/tpm/
H A DKconfig33 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/linux/drivers/acpi/acpica/
Dutstrtoul64.c
/openbmc/u-boot/lib/efi_loader/
H A Defi_device_path_utilities.c21 * 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 DAOM-Patent-License-1.045 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/docs/designs/mctp/
H A Dmctp-standards.svg71 …: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/openbmc/poky/meta/recipes-sato/sato-icon-theme/
H A Dicon-naming-utils_0.8.90.bb5 names specified in the Icon Naming Specification. The Icon Naming \
7 icon names proposed in the Icon Naming Specification, and generate the \
9 Naming Specification provides a standard list of common icon contexts \
11 environment or application that implements the naming specification. "
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-apispec_6.8.2.bb1 …MMARY = "A pluggable API specification generator. Currently supports the OpenAPI Specification (f.…
/openbmc/linux/Documentation/RCU/Design/Requirements/
DReadersPartitionGP1.svg
DGPpartitionReaders1.svg
/openbmc/libcper/cli-app/
H A Dcper-convert.c49 } else if (strcmp(argv[i], "--specification") == 0 && in main()
51 //Specification file. in main()
56 //Invalidates specification file. in main()
215 …printf("\n:: to-cper cper.json --out file.name [--no-validate] [--debug] [--specification some/spe… in print_help()
219 …ault, the provided JSON will try to be validated against a specification. If no specification file… in print_help()
220 …printf("\tis provided with '--specification', then it will default to 'argv[0] + /specification/cp… in print_help()
223 …printf("\tIf '--debug' is set, then debug output for JSON specification parsing will be printed to… in print_help()
/openbmc/linux/Documentation/devicetree/bindings/input/touchscreen/
Dzet6223.txt
/openbmc/linux/drivers/infiniband/ulp/srpt/
Dib_dm_mad.h

12345678910>>...84