| /openbmc/linux/Documentation/gpu/ |
| H A D | afbc.rst | 31 * Component 0: R
32 * Component 1: G
33 * Component 2: B
42 * Component 0: R(8)
43 * Component 1: G(8)
44 * Component 2: B(8)
45 * Component 3: A(8)
49 * Component 0: R(8)
50 * Component 1: G(8)
51 * Component 2: B(8)
[all …]
|
| H A D | kms-properties.csv | 4 ,TV,“subconnector”,ENUM,"{ ""Unknown"", ""Composite"", ""SVIDEO"", ""Component"", ""SCART"" }",Conn…
5 ,,“select subconnector”,ENUM,"{ ""Automatic"", ""Composite"", ""SVIDEO"", ""Component"", ""SCART"" …
|
| /openbmc/linux/Documentation/driver-api/pldmfw/ |
| H A D | file-format.rst | 25 | Component Info |
33 | Component Image 1 |
37 | Component Image 2 |
45 | Component Image N |
69 | Component Bitmap Length |
136 Component Info
150 | Component Count |
154 | Component 1 |
158 | Component 2 |
166 | Component N |
[all …]
|
| /openbmc/linux/drivers/slimbus/ |
| H A D | Kconfig | 17 tristate "Qualcomm SLIMbus Manager Component"
20 Select driver if Qualcomm's SLIMbus Manager Component is
24 tristate "Qualcomm SLIMbus Satellite Non-Generic Device Component"
32 Component is programmed using Linux kernel.
|
| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_fru.robot | 26 ${ipmi_fru_component_info}= Get Component FRU Info ${COMPONENT_NAME_OF_POWER_SUPPLY}
58 Compare IPMI And Redfish FRU Component ${ipmi_fru_sub_component}
63 Compare IPMI And Redfish FRU Component
64 [Documentation] Compare IPMI And Redfish FRU Component data objects.
|
| H A D | test_ipmi_sdr.robot | 121 ${component_uri_list}= Get Component URIs auto_reboot
138 ${component_uri_list}= Get Component URIs TPMEnable
281 Get Component URIs
295 # component_name Component name (e.g. "core", "dimm", etc.).
309 # component_name Component name (e.g. "cpu0_core0", "dimm0", etc.).
345 # component_name Component name (e.g. "cpu0/core0", "dimm0", etc.).
375 # component_name Component name (e.g. "core", "dimm", etc.).
377 ${component_uri_list}= Get Component URIs ${component_name}
|
| /openbmc/openbmc-test-automation/openpower/ipmi/ |
| H A D | test_ipmi_sdr.robot | 23 ${component_uri_list}= Get Component URIs turbo_allowed
37 Get Component URIs
51 # component_name Component name (e.g. "core", "dimm", etc.).
65 # component_name Component name (e.g. "cpu0_core0", "dimm0", etc.).
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-switchtec | 18 Description: Component identifier as stored in the hardware (eg. PM8543)
27 Description: Component revision stored in the hardware (read only)
35 Description: Component vendor as stored in the hardware (eg. MICROSEM)
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | chassis.hpp | 28 Component, enumerator
101 {ChassisType::Component, "Component"},
|
| /openbmc/openbmc-test-automation/openpower/vpd/ |
| H A D | test_vpd_tool.robot | 15 ${DR_WRITE_VALUE} XYZ Component
28 # Component Field
34 Verify VPD Component Read
41 Verify VPD Component Read Operation ${component}
77 Verify VPD Component Read Operation
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | component.rst | 4 Component Helper for Aggregate Drivers
|
| /openbmc/pldm/tools/fw-update/ |
| H A D | README.md | 125 ## Component Image Information Area
128 of type List. Each List entry corresponds to an Individual Component Image
132 - ComponentImageInformation: which is a list of Individual Component Image
142 - supported options are Force Update and Use Component Comparison Stamp.
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | IEC-Code-Components-EULA | 15 - The user of Code Components shall attribute each such Code Component to IEC and identify
24 Component.
|
| /openbmc/linux/net/mctp/ |
| H A D | Kconfig | 6 Management Component Transport Protocol (MCTP) is an in-system
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-rgb.rst | 50 Less Than 8 Bits Per Component
75 .. flat-table:: RGB Formats With Less Than 8 Bits Per Component
642 8 Bits Per Component
660 .. flat-table:: RGB Formats With 8 Bits Per Component
766 10 Bits Per Component
784 .. flat-table:: RGB Formats 10 Bits Per Color Component
956 12 Bits Per Component
967 .. flat-table:: RGB Formats With 12 Bits Per Component
|
| /openbmc/libcper/specification/document/ |
| H A D | cper-json-specification.tex | 1670 % PCI/PCI-X Component error section.
1671 \section{PCI/PCI-X Component Error Section}
1673 … JSON format for a single PCI/PCI-X Component Error Section from a CPER record. The GUID used for …
1675 validationBits & object & A PCI/PCI-X Component Error Validation structure, as defined in Subsectio…
1679 idInfo & object & A PCI/PCI-X Component ID structure, as defined in Subsection \ref{subsection:pcic…
1685 registerDataPairs & array & An array of PCI/PCI-X Component Register Pair structures, as defined in…
1686 \jsontableend{PCI/PCI-X Component Error structure field table.}
1688 % PCI/PCI-X Component error validation structure.
1689 \subsection{PCI/PCI-X Component Error Validation Structure}
1691 This structure describes which fields within a PCI/PCI-X Component Error section (\ref{section:pcic…
[all …]
|
| /openbmc/libpldm/tests/fuzz/ |
| H A D | fd.dict | 13 # Update Component. Similar to pass_comp at the start
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/mctp/ |
| H A D | mctp_2.1.bb | 1 SUMMARY = "Management Component Control Protocol utilities"
|
| /openbmc/openbmc/poky/meta/recipes-support/icu/ |
| H A D | icu_76-1.bb | 1 SUMMARY = "International Component for Unicode libraries"
2 DESCRIPTION = "The International Component for Unicode (ICU) is a mature, \
|
| /openbmc/openbmc/poky/meta/recipes-extended/acpica/ |
| H A D | acpica_20240827.bb | 2 DESCRIPTION = "The ACPI Component Architecture (ACPICA) project provides an \
|
| /openbmc/linux/Documentation/firmware-guide/acpi/dsd/ |
| H A D | phy.rst | 76 a) Silicon Component
98 b) Platform Component
|
| /openbmc/bmcweb/test/redfish-core/lib/ |
| H A D | chassis_test.cpp | 74 chassis::ChassisType::Component, in TEST()
|
| /openbmc/linux/drivers/staging/greybus/Documentation/firmware/ |
| H A D | firmware-management | 40 ; (Optional) Component Authentication Protocol (CAP) on CPort 4
186 The Component Authentication Protocol interacts with Userspace using the
290 cryptographic certificates held by the Interface for use in Component
|
| /openbmc/linux/Documentation/userspace-api/media/ |
| H A D | glossary.rst | 58 Hardware Component
64 A group of :term:`hardware components <Hardware Component>` that
|
| /openbmc/openbmc/poky/ |
| H A D | MAINTAINERS.md | 30 Component/Subsystem Maintainers
|