Home
last modified time | relevance | path

Searched refs:specification (Results 1 – 25 of 664) sorted by relevance

12345678910>>...27

/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
/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
20 "invalid date format in specification: #{date.inspect}")
/openbmc/linux/drivers/staging/greybus/
H A DKconfig9 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/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/linux/Documentation/ABI/testing/
H A Dsysfs-bus-i3c22 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
H A Dsysfs-bus-pci-devices-pvpanic12 from pvpanic device specification:
26 Also refer to pvpanic device specification.
/openbmc/qemu/tests/tcg/s390x/
H A DMakefile.softmmu-target36 include $(S390X_SRC)/pgm-specification.mak
37 $(PGM_SPECIFICATION_TESTS): pgm-specification-softmmu.o
38 $(PGM_SPECIFICATION_TESTS): LDFLAGS+=pgm-specification-softmmu.o
H A DMakefile.target61 include $(S390X_SRC)/pgm-specification.mak
62 $(PGM_SPECIFICATION_TESTS): pgm-specification-user.o
63 $(PGM_SPECIFICATION_TESTS): LDFLAGS+=pgm-specification-user.o
/openbmc/linux/drivers/char/tpm/
H A DKconfig14 implements the Trusted Computing Group's specification,
18 userspace enablement piece of the specification, can be
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
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
84 (I2C interface) specification and connected to an I2C bus master,
95 TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO
96 specification (TPM2.0) say Yes and it will be accessible from
124 TCG TIS 1.2 TPM specification and Infineon's I2C Protocol Stack
[all …]
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-apispec_6.8.1.bb1 …MMARY = "A pluggable API specification generator. Currently supports the OpenAPI Specification (f.…
/openbmc/linux/Documentation/nvme/
H A Dfeature-and-quirk-policy.rst20 - the NVMe Base specification
23 - the NVMe Management Interface specification
33 does not aim to implement every feature in the specification. Every additional
42 specification, or in a ratified Technical Proposal (TP) that is
54 maintainers and get feedback on specification changes that are intended
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/cim-schema/
H A Dcim-schema.inc4 consists of a specification and a schema. The specification defines the\
/openbmc/openbmc/poky/meta/recipes-extended/gperf/gperf/
H A D1862c6e57a308a05889c80c048dbc58bdc378dcb.patch104 + specification.
105 + FILE_SYSTEM_PREFIX_LEN(Filename) length of the device specification
110 + 1 when a non-empty device specification
113 + 0 when a non-empty device specification
115 + 0 when device specification don't exist.
125 + or directory specification.
/openbmc/linux/drivers/cxl/
H A DKconfig23 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/docs/specs/
H A Dtpm.rst14 following the Trusted Computing Group's specification "TCG PC Client
16 1.3, 21 March 2013. (see the `TIS specification`_, or a later version
40 Computing Group's specification "TCG PC Client Platform TPM Profile
42 22, 2017. (see the `CRB specification`_, or a later version of it)
100 specification "TCG ACPI Specification" Family "1.2" and "2.0", Level
101 00 Revision 00.37. (see the `ACPI specification`_, or a later version
109 `PPI specification`_)
112 the TPM upon reboot. The PPI specification defines the operation
121 The PPI specification defines a set of mandatory and optional
289 commands can be sent. (see the `SWTPM protocol`_ specification)
[all …]
/openbmc/linux/drivers/net/mctp/
H A DKconfig12 serial line-discipline, as defined by DMTF specification "DSP0253 -
33 from DMTF specification DSP0237. A MCTP protocol network device is
41 from DMTF specification DSP0233.
/openbmc/linux/Documentation/devicetree/bindings/input/touchscreen/
H A Dektf2127.txt6 - interrupts : interrupt specification for the ektf2127 interrupt
7 - power-gpios : GPIO specification for the pin connected to the
/openbmc/linux/Documentation/virt/coco/
H A Dtdx-guest.rst38 the TDX Module v1.0 specification, section titled "TDG.MR.REPORT", it is not
52 The driver is based on TDX module specification v1.0 and TDX GHCI specification v1.0.
H A Dsev-guest.rst83 contain the format described in the SEV-SNP specification. See the SEV-SNP
84 specification for further details.
98 SEV-SNP firmware to derive the key. See SEV-SNP specification for further details
102 the SEV-SNP specification for further details.
125 See GHCB specification for further detail on how to parse the certificate blob.
159 SEV-SNP and GHCB specification: developer.amd.com/sev
/openbmc/u-boot/doc/device-tree-bindings/video/bridge/
H A Dps8622.txt6 - sleep-gpios: OF device-tree gpio specification for PD_ pin.
7 - reset-gpios: OF device-tree gpio specification for RST_ pin.
/openbmc/linux/Documentation/dev-tools/
H A Dktap.rst8 by a number of projects. It's website and specification are found at this `link
11 which don't align with the original TAP specification. Thus, a "Kernel TAP"
13 This specification describes the generally accepted format of KTAP as it is
30 there is a stagnant draft specification for TAP14, KTAP diverges from this in
245 The TAP14 specification does permit nested tests, but instead of using another
304 - The TAP specification:
305 https://testanything.org/tap-version-13-specification.html
306 - The (stagnant) TAP version 14 specification:
307 https://github.com/TestAnything/Specification/blob/tap-14-specification/specification.md
/openbmc/linux/Documentation/driver-api/soundwire/
H A Dsummary.rst31 direction is enabled by the specification). Bandwidth restrictions to
58 The MIPI SoundWire specification uses the term 'device' to refer to a Master
133 MIPI specification, so Bus calls the "sdw_master_port_ops" callback
141 The MIPI specification requires each Slave interface to expose a unique
154 board-file, ACPI or DT. The MIPI Software specification defines additional
198 SoundWire MIPI specification 1.1 is available at:
201 SoundWire MIPI DisCo (Discovery and Configuration) specification is
/openbmc/linux/Documentation/devicetree/bindings/mtd/
H A Dlpc32xx-mlc.txt6 - interrupts: The NAND interrupt specification
7 - gpios: GPIO specification for NAND write protect
/openbmc/linux/Documentation/userspace-api/netlink/
H A Dnetlink-raw.rst4 Netlink specification support for raw Netlink families
9 specification.
/openbmc/linux/Documentation/devicetree/bindings/leds/
H A Dleds-ns2.txt9 - cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification.
10 - slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification.

12345678910>>...27