| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | CollectionCapabilities.v1_4_1.json | 8 … "description": "This type describes a capability of a collection for a specific use case.",
39 …longDescription": "This property shall contain an enumerated value that describes the use case for…
52 "description": "This type describes the capabilities of a collection.",
127 …perty shall contain a link to a resource collection that this structure describes. A client can u…
146 …"ComputerSystemComposition": "This capability describes a client creating a new computer system re…
147 …"ComputerSystemConstrainedComposition": "This capability describes a client creating a new compute…
148 …"RegisterResourceBlock": "This capability describes a client creating a new resource block from an…
149 …"ResourceBlockComposition": "This capability describes a client creating a new resource block from…
150 …"ResourceBlockConstrainedComposition": "This capability describes a client creating a new resource…
151 …"VolumeCreation": "This capability describes a client creating a new volume resource as part of an…
|
| H A D | Manifest.v1_1_2.json | 26 …his type describes a manifest containing a set of requests to be fulfilled. The manifest contains…
222 …"ComposeResource": "A stanza that describes the desired end state for a composed resource block. …
223 …"ComposeSystem": "A stanza that describes the desired end state for computer system composition op…
226 "OEM": "A stanza that describes an OEM-specific request.",
230 …"ComposeResource": "This value shall indicate a stanza that describes a composed resource block. …
231 …"ComposeSystem": "This value shall indicate a stanza that describes the specific, constrained, or …
234 …"OEM": "This value shall indicate a stanza that describes an OEM-specific request. The `OEMStanza…
|
| /openbmc/u-boot/doc/ |
| H A D | README.bus_vcxk | 45 describes the acknowledge line from vcxk hardware
48 describes the enable line to vcxk hardware
51 describes the invert line to vcxk hardware
54 describes the reset line to vcxk hardware
57 describes the request line to vcxk hardware
|
| /openbmc/u-boot/arch/arm/mach-k3/ |
| H A D | Kconfig | 19 Describes the total size of the MCU MSRAM. This doesn't
28 Describes the maximum size of the image that ROM can download
35 Describes the base address of MCU Scratchpad RAM.
41 Describes the size of MCU Scratchpad RAM.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/geany/geany/ |
| H A D | geany-2.0-gcc15.patch | 80 // The License.txt file describes the conditions under which this software may be distributed.
89 // The License.txt file describes the conditions under which this software may be distributed.
100 // The License.txt file describes the conditions under which this software may be distributed.
109 // The License.txt file describes the conditions under which this software may be distributed.
120 // The License.txt file describes the conditions under which this software may be distributed.
130 // The License.txt file describes the conditions under which this software may be distributed.
140 // The License.txt file describes the conditions under which this software may be distributed.
|
| /openbmc/u-boot/include/ |
| H A D | board.h | 50 * get_bool() - Read a specific bool data value that describes the
61 * get_int() - Read a specific int data value that describes the
72 * get_str() - Read a specific string data value that describes the
96 * board_get_bool() - Read a specific bool data value that describes the
107 * board_get_int() - Read a specific int data value that describes the
118 * board_get_str() - Read a specific string data value that describes the
|
| /openbmc/libcper/specification/document/ |
| H A D | cper-json-specification.tex | 83 This structure describes the JSON format of the standard CPER header as defined in section N.2.1 of…
120 This structure describes the error severity of a single CPER record.
130 This structure describes a bitfield for validating the fields of the header of a single CPER record.
142 This structure describes the notification type of a single CPER record.
152 This structure describes the enabled flag on a given CPER record header.
162 This section describes the JSON format of a single CPER record section descriptor as defined by sec…
166 …t64 & The offset (in bytes) of the section body this section descriptor describes from the base of…
191 This structure describes the enabled flags on a given CPER section descriptor.
212 This section describes generic CPER structures that are re-used throughout the specification.
217 This structure describes the revision of a single CPER record or sub-structure.
[all …]
|
| /openbmc/u-boot/drivers/ddr/marvell/a38x/ |
| H A D | xor.h | 18 * This structure describes address space window. Window base can be
27 /* This structure describes SoC units address decode window */
36 * This enumerator describes the type of functionality the XOR channel
53 * This enumerator describes the set of commands that can be applied on
|
| /openbmc/u-boot/test/py/ |
| H A D | pytest.ini | 9 boardspec: U-Boot: Describes the set of boards a test can/can't run on.
10 buildconfigspec: U-Boot: Describes Kconfig/config-header constraints.
|
| /openbmc/u-boot/drivers/ddr/marvell/axp/ |
| H A D | xor.h | 14 * This enumerator describes the type of functionality the XOR channel
24 * This enumerator describes the set of commands that can be applied on
40 * This enumerator describes the set of state conditions.
|
| /openbmc/phosphor-networkd/docs/ |
| H A D | Network-Configuration.md | 19 1. SystemConfiguration: This describes the system-specific parameters.
20 2. EthernetInterface: This describes the interface-specific parameters.
21 3. IP: This describes the IP address-specific parameters.
22 4. IPProtocol: This describes the IP protocol type (IPv4/IPv6).
23 5. VLANInterface: This describes the VLAN-specific properties.
24 6. Bond: This describes the interface bonding parameters.
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/ipzvpd/ |
| H A D | README.md | 8 The [OpenPower VPD][1] format is quite similar to the IPZ format and describes
11 Also refer to the [VPD Collection design document][2] that describes how the VPD
|
| /openbmc/entity-manager/schemas/ |
| H A D | README.md | 11 most schema describes a single object or an array of objects.
42 The probe property describes the event which will cause entity manager to export
47 The exposes property describes the configuration data at its most specific
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | CollectionCapabilities_v1.xml | 33 …<Annotation Term="OData.Description" String="This type describes the capabilities of a collection.…
51 …<Annotation Term="OData.Description" String="This type describes a capability of a collection for …
63 …scription" String="This property shall contain an enumerated value that describes the use case for…
75 …<Annotation Term="OData.Description" String="This capability describes a client creating a new com…
78 …<Annotation Term="OData.Description" String="This capability describes a client creating a new com…
89 …<Annotation Term="OData.Description" String="This capability describes a client creating a new vol…
92 …<Annotation Term="OData.Description" String="This capability describes a client creating a new res…
103 …<Annotation Term="OData.Description" String="This capability describes a client creating a new res…
114 …<Annotation Term="OData.Description" String="This capability describes a client creating a new res…
132 …perty shall contain a link to a resource collection that this structure describes. A client can u…
|
| H A D | Manifest_v1.xml | 29 …his type describes a manifest containing a set of requests to be fulfilled. The manifest contains…
106 …<Annotation Term="OData.Description" String="A stanza that describes the desired end state for com…
107 …"OData.LongDescription" String="This value shall indicate a stanza that describes the specific, co…
114 …<Annotation Term="OData.Description" String="A stanza that describes the desired end state for a c…
115 …"OData.LongDescription" String="This value shall indicate a stanza that describes a composed resou…
122 … <Annotation Term="OData.Description" String="A stanza that describes an OEM-specific request."/>
123 …"OData.LongDescription" String="This value shall indicate a stanza that describes an OEM-specific …
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Network/ |
| H A D | README.md | 19 1. SystemConfiguration: This describes the system-specific parameters.
20 2. EthernetInterface: This describes the interface specific parameters.
21 3. IP: This describes the IP address specific parameters.
22 4. IPProtocol: This describes the IP protocol type(IPv4/IPv6).
23 5. VLANInterface: This describes the VLAN specific properties.
24 6. Bond: This describes the interface bonding parameters.
|
| /openbmc/qemu/docs/system/ |
| H A D | device-emulation.rst | 10 used to describes devices within QEMU.
26 A front end is often paired with a back end, which describes how the
56 The back end describes how the data from the emulated device will be
|
| /openbmc/u-boot/doc/device-tree-bindings/nand/ |
| H A D | nvidia,tegra20-nand.txt | 4 (there isn't yet a generic binding in Linux, so this describes what is in
6 a binding that describes this hardware. But agreeing a binding in Linux in
|
| /openbmc/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | nvidia,tegra186-gpio.txt | 6 differences. Hence, this document describes closely related but different
30 Tegra HW documentation describes a unified naming convention for all GPIOs
43 describes the port-level mapping. In that file, the naming convention for ports
90 order the HW manual describes them. The number of entries required varies
|
| /openbmc/u-boot/arch/nds32/include/asm/ |
| H A D | setup.h | 58 /* describes how the ramdisk will be used in kernel */
70 * describes where the compressed ramdisk image lives (virtual address)
74 /* describes where the compressed ramdisk image lives (physical address) */
|
| /openbmc/u-boot/doc/device-tree-bindings/video/ |
| H A D | rockchip-lvds.txt | 16 This describes how the color bits are laid out in the
20 <LVDS_OUTPUT_DUAL>, This describes the output face.
|
| H A D | tegra20-dc.txt | 4 (there isn't yet a generic binding in Linux, so this describes what is in
20 The panel node describes the panel itself. This has the properties listed in
|
| /openbmc/u-boot/arch/x86/include/asm/fsp/ |
| H A D | fsp_hob.h | 20 * Describes the format and size of the data inside the HOB.
30 * Describes all memory ranges used during the HOB producer phase that
31 * exist outside the HOB list. This HOB type describes how memory is used,
99 * Describes the resource properties of all fixed, nonrelocatable resource
|
| /openbmc/u-boot/doc/device-tree-bindings/firmware/ |
| H A D | ti,sci.txt | 19 The TI-SCI node describes the Texas Instrument's System Controller entity node.
22 functionality as may be required for the SoC. This hierarchy also describes the
|
| /openbmc/google-misc/subprojects/libcr51sign/src/ |
| H A D | libcr51sign_mauv.c | 35 // @param[in] ctx context which describes the image and holds opaque private
78 // @param[in] ctx context which describes the image and holds opaque private
179 // @param[in] ctx context which describes the image and holds opaque private
334 // @param[in] ctx context which describes the image and holds opaque private
401 // @param[in] ctx context which describes the image and holds opaque private
439 // @param[in] ctx context which describes the image and holds opaque private
|