| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | storage_device_message_registry.hpp | 43 "A charging condition for the battery located in '%1' was detected.",
55 "A failure condition for the battery located in '%1' was detected.",
67 "The battery located in '%1' is missing.",
79 "The health of the battery located in '%1' has changed to OK.",
91 …"A degraded condition for the storage controller located in '%1' was detected due to reason '%2'.",
104 "A failure condition for the storage controller located in '%1' was detected.",
116 "The health of the storage controller located in '%1' has changed to OK.",
128 "A password was entered for the storage controller located in '%1'.",
140 "The storage controller located in '%1' requires a password.",
152 … "A degraded condition for the controller port located in '%1' was detected due to reason '%2'.",
[all …]
|
| /openbmc/linux/drivers/net/ethernet/agere/ |
| H A D | et131x.h | 88 * located at address 0x0010
147 /* Loopback reg located at address 0x0034
153 * Located at address 0x0000
184 * located at address 0x1004
189 * located at address 0x1008
194 * map. Located at address 0x100C
237 * Located at address 0x1000
272 * Located at address 0x2000
301 * located at address 0x2004
306 * located at address 0x2008
[all …]
|
| /openbmc/linux/include/asm-generic/ |
| H A D | sections.h | 148 * is_kernel_core_data - checks if the pointer address is located in the
153 * Returns: true if the address is located in .data or .bss, false otherwise.
170 * is_kernel_rodata - checks if the pointer address is located in the
175 * Returns: true if the address is located in .rodata, false otherwise.
184 * is_kernel_inittext - checks if the pointer address is located in the
189 * Returns: true if the address is located in .init.text, false otherwise.
198 * __is_kernel_text - checks if the pointer address is located in the
203 * Returns: true if the address is located in .text, false otherwise.
213 * __is_kernel - checks if the pointer address is located in the kernel range
217 * Returns: true if the address is located in the kernel range, false otherwise.
|
| /openbmc/linux/drivers/net/ethernet/intel/ |
| H A D | Kconfig | 30 can be located at:
48 to the Adapter & Driver ID Guide that can be located at:
68 can be located at:
96 to the Adapter & Driver ID Guide that can be located at:
132 Driver ID Guide that can be located at:
151 to the Adapter & Driver ID Guide that can be located at:
203 adapter, go to the Adapter & Driver ID Guide that can be located at:
231 to the Adapter & Driver ID Guide that can be located at:
264 & Driver ID Guide that can be located at:
290 to the Adapter & Driver ID Guide that can be located at:
[all …]
|
| /openbmc/u-boot/arch/x86/include/asm/fsp/ |
| H A D | fsp_support.h | 102 * If the GUID HOB is located, the length will be updated.
116 * If the GUID HOB is located, the length will be updated.
127 * If the GUID HOB is located, the length will be updated.
160 * If the GUID HOB is located, the length will be updated.
174 * If the HOB is located, the length will be updated.
186 * If the HOB is located, the length will be updated.
198 * If the HOB is located, the length will be updated.
|
| /openbmc/linux/Documentation/devicetree/bindings/watchdog/ |
| H A D | mpc8xxx-wdt.txt | 17 On the 83xx, it is located at offset 0x910
18 On the 86xx, it is located at offset 0xe0094
19 On the 8xx, it is located at offset 0x288
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | marvell-orion-net.txt | 43 - marvell,tx-sram-addr: address of transmit descriptor buffer located in SRAM.
44 - marvell,tx-sram-size: size of transmit descriptor buffer located in SRAM.
46 - marvell,rx-sram-addr: address of receive descriptor buffer located in SRAM.
47 - marvell,rx-sram-size: size of receive descriptor buffer located in SRAM.
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | smsc47b397.rst | 40 pair is located at the HWM Base Address + 0 and the HWM Base Address + 1. The
46 The temperature information is located in the following registers:
70 The fan speed information is located in the following registers:
121 In configuration mode, the INDEX PORT is located at the CONFIG PORT address and
146 The following is an example of how to read the SIO Device ID located at 0x20:
173 The following is an example of how to read the HWM Base Address located in
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | binderfs.rst | 8 located in a new binderfs instance are independent of binder devices located in
62 binder device located under /dev/binderfs with the chosen name.
80 features supported by the binder driver can be located under
|
| /openbmc/linux/drivers/staging/media/omap4iss/ |
| H A D | iss.h | 156 * @res: memory resource in which the register is located
171 * @res: memory resource in which the register is located
185 * @res: memory resource in which the register is located
201 * @res: memory resource in which the register is located
217 * @res: memory resource in which the register is located
|
| /openbmc/openbmc/poky/documentation/toaster-manual/ |
| H A D | start.rst | 28 dependencies. The requirements file is located in the ``bitbake``
29 directory, which is located in the root directory of the
44 located in ``$HOME/.local``. To see what packages have been installed
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | command_syntax_extensions.txt | 51 Ad. 2. Boot kernel image located at <addr1>.
70 Ad. 5. Boot kernel image located at <addr1> with initrd loaded with ramdisk
141 - boot kernel "kernel-1" stored in a new uImage located at 200000:
144 - boot configuration "cfg-1" from a new uImage located at 200000:
147 - boot configuration "cfg-1" with extra "cfg-2" from a new uImage located
156 "fdt-1", both stored in some other new uImage located at 800000:
|
| /openbmc/linux/Documentation/kbuild/ |
| H A D | modules.rst | 99 The directory where the kernel source is located.
107 located.
117 The default will build the module(s) located in the current
175 located in Documentation/kbuild/makefiles.rst.
328 of the kernel that are located in different directories, then
334 include/scsi; and architecture specific headers are located
340 To include a header file located under include/linux/, simply
352 include/ directory where their source is located, although this
397 As you can see, kbuild knows how to handle object files located
407 file is located.
|
| /openbmc/linux/drivers/dma/dw/ |
| H A D | Kconfig | 24 Support the Renesas RZ/N1 DMAMUX which is located in front of
25 the Synopsys DesignWare AHB DMA controller located on Renesas
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-rf-tuner.rst | 68 signal path. It is located very close to tuner antenna input. Used
76 located inside mixer block, where RF signal is down-converted by the
82 located on output of RF tuner. It controls signal level of
|
| /openbmc/linux/drivers/net/dsa/mv88e6xxx/ |
| H A D | global1_atu.c | 144 /* ATU DBNum[7:4] are located in ATU Control 15:12 */ in mv88e6xxx_g1_atu_op()
156 /* ATU DBNum[5:4] are located in ATU Operation 9:8 */ in mv88e6xxx_g1_atu_op()
160 /* ATU DBNum[3:0] are located in ATU Operation 3:0 */ in mv88e6xxx_g1_atu_op()
192 /* ATU DBNum[7:4] are located in ATU Control 15:12 */ in mv88e6xxx_g1_atu_fid_read()
200 /* ATU DBNum[5:4] are located in ATU Operation 9:8 */ in mv88e6xxx_g1_atu_fid_read()
204 /* ATU DBNum[3:0] are located in ATU Operation 3:0 */ in mv88e6xxx_g1_atu_fid_read()
|
| /openbmc/linux/Documentation/devicetree/bindings/mtd/partitions/ |
| H A D | u-boot.yaml | 11 located on some kind of flash device.
14 located in a (usually standalone) block of data.
|
| /openbmc/webui-vue/docs/guide/coding-standards/ |
| H A D | readme.md | 24 Any overrides to a rule are located in the ESLint configuration file,
25 `.eslintrc.js`, located in the root directory.
|
| /openbmc/openbmc/meta-arm/meta-arm/classes/ |
| H A D | apply_local_src_patches.bbclass | 1 # This class is to be inherited by recipes where there are patches located inside
5 # LOCAL_SRC_PATCHES_INPUT_DIR is the directory from where the patches are located
|
| /openbmc/qemu/docs/devel/ |
| H A D | ebpf_rss.rst | 56 RSS program located in ebpf/rss.bpf.skeleton.h generated by bpftool.
58 Initially, the eBPF program was compiled by clang and source code located at tools/ebpf/rss.bpf.c.
73 eBPF RSS loading functionality located in ebpf/ebpf_rss.c and ebpf/ebpf_rss.h.
|
| /openbmc/linux/drivers/gpu/drm/i915/gt/shaders/ |
| H A D | README | 28 * IGT gpu tools source code is located on your home directory (~) as ~/igt
29 * Mesa source code is located on your home directory (~) as ~/mesa
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/fans/phosphor-fan-control-zone-config/witherspoon/ |
| H A D | zones.yaml | 31 PCI cards located behind the GPU exhaust that
79 PCI cards located behind the GPU exhaust that
|
| /openbmc/openbmc/poky/meta/lib/oeqa/core/ |
| H A D | README | 5 This is version 2 of the OEQA framework. Base clases are located in the
32 Also, a new 'oe-test' runner is located under 'scripts', allowing scans for components
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Chassis.v1_26_0.json | 104 … "description": "The link to the collection of controls located in this chassis.",
194 …"description": "The link to the collection of fabric adapters located in this chassis that provide…
269 … "description": "The link to the collection of leak detectors located in this chassis.",
335 … "description": "The link to the collection of media controllers located in this chassis.",
343 …"description": "The link to the collection of memory located in this chassis that belong to fabric…
350 …"description": "The link to the collection of memory domains located in this chassis that belong t…
393 … "description": "The link to the collection of PCIe devices located in this chassis.",
463 …"description": "The link to the collection of processors located in this chassis that belong to fa…
489 …"description": "The link to the collection of sensors located in the equipment and sub-components.…
490 …resource collection of type `SensorCollection` that contains the sensors located in the chassis an…
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Chassis.v1_26_0.json | 104 … "description": "The link to the collection of controls located in this chassis.",
194 …"description": "The link to the collection of fabric adapters located in this chassis that provide…
269 … "description": "The link to the collection of leak detectors located in this chassis.",
335 … "description": "The link to the collection of media controllers located in this chassis.",
343 …"description": "The link to the collection of memory located in this chassis that belong to fabric…
350 …"description": "The link to the collection of memory domains located in this chassis that belong t…
393 … "description": "The link to the collection of PCIe devices located in this chassis.",
463 …"description": "The link to the collection of processors located in this chassis that belong to fa…
489 …"description": "The link to the collection of sensors located in the equipment and sub-components.…
490 …resource collection of type `SensorCollection` that contains the sensors located in the chassis an…
[all …]
|