| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | nfp.rst | 46 - stored, running
49 - stored, running
52 - stored, running
55 - stored, running
58 - stored, running
61 - stored, running
64 - stored, running
|
| H A D | bnxt.rst | 66 - stored, running
69 - stored, running
72 - stored, running
78 - stored, running
81 - stored, running
|
| /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)
44 Description: Device version as stored in the hardware (read only)
76 Description: Product identifier as stored in the hardware (eg. PSX 48XG3)
85 Description: Product revision stored in the hardware (eg. RevB)
94 Description: Product vendor as stored in the hardware (eg. MICROSEM)
|
| H A D | sysfs-class-rc-nuvoton | 6 Reading this file returns the stored CIR wakeup sequence.
12 Note: Some systems reset the stored wakeup sequence to a
|
| /openbmc/linux/Documentation/filesystems/ext4/ |
| H A D | attributes.rst | 6 Extended attributes (xattrs) are typically stored in a separate data
23 attribute's value to be stored in a separate data block, though as of
29 Extended attributes, when stored after the inode, have a header
89 long. When stored in an external block, the ``struct ext4_xattr_entry``
90 entries must be stored in sorted order. The sort order is
92 Attributes stored inside an inode do not need be stored in sorted order.
113 - Location of this attribute's value on the disk block where it is stored.
120 - The inode where the value is stored. Zero indicates the value is in the
141 are stored starting at the end of the block and grow towards the
188 POSIX ACLs are stored in a reduced version of the Linux kernel (and
[all …]
|
| H A D | checksums.rst | 11 lower 16 bits are stored. Enabling the 64bit feature increases the data
12 structure size so that full 32-bit checksums can be stored for many data
62 - UUID + the entire bitmap. Checksums are stored in the group descriptor,
72 descriptor). In all cases, only the lower 16 bits are stored.
|
| H A D | verity.rst | 12 stored after the end of the file data itself, in the following format:
19 <fsverity_merkle_tree>`, with the tree levels stored in order from
20 root to leaf, and the tree blocks within each level stored in their
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/amd/ |
| H A D | pds_core.rst | 41 stored:
61 - stored
62 - Version of firmware stored in the goldfw slot
64 - stored
65 - Version of firmware stored in the mainfwa slot
67 - stored
68 - Version of firmware stored in the mainfwb slot
|
| /openbmc/u-boot/doc/ |
| H A D | README.at91 | 20 U-Boot environment variables can be stored at different places:
42 U-Boot environment variables can be stored at different places:
63 U-Boot environment variables can be stored at different places:
86 U-Boot environment variables can be stored at different places:
103 U-Boot environment variables can be stored at different places:
120 U-Boot environment variables can be stored at different places:
141 U-Boot environment variables can be stored at different places:
|
| H A D | README.sha1 | 16 calculates and prints the SHA1 sum, from the Image stored in Flash
19 check, if the SHA1 sum from the Image stored in Flash is correct
30 (for this example we use the Image from Flash, stored at 0xfffa0000 and
36 The SHA1 sum is stored in Flash at:
|
| H A D | README.enetaddr | 6 and stored. This document covers proper usage of each location and the moving
13 Here are the places where MAC addresses might be stored:
54 If the hardware design mandates that the MAC address is stored in some special
89 Look up an environment variable and convert the stored address. If the address
99 /* enetaddr is now set to the value stored in the ethaddr env var */
|
| /openbmc/linux/drivers/char/mwave/ |
| H A D | README | 18 If the dsp irq has not been setup and stored in bios by the
23 If the dsp io range has not been setup and stored in bios by the
28 If the mwave's uart irq has not been setup and stored in bios by the
33 If the uart io range has not been setup and stored in bios by the
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | squashfs.rst | 110 these are stored here.
133 information has to be stored.
138 Like inodes, directories are packed into compressed metadata blocks, stored
170 of each datablock is stored in a block list contained within the
189 fragment lookup table is itself stored compressed into metadata blocks.
199 stored compressed into metadata blocks. A second index table is used to
213 This table is stored compressed into metadata blocks. A second index table is
221 for each inode are stored in a list, each list entry containing a type,
225 is stored inline (in which case the value field contains the xattr value),
226 or if it is stored out of line (in which case the value field stores a
[all …]
|
| H A D | qnx6.rst | 55 Each of these root nodes holds information like total size of the stored
68 Data leaves are always on the lowest level. So no data is stored on upper
100 The filesize is stored 64bit. Inode counting starts with 1. (while long
119 record plus the longfile inode number also stored in that record.
143 Long filenames are stored in a separate addressing tree. The staring point
151 is a limit of 510 bytes for the actual filename stored.
156 The qnx6fs filesystem allocation bitmap is stored in a tree under bitmap
|
| /openbmc/docs/architecture/code-update/ |
| H A D | flash-layout.md | 18 are stored in the bootloader environment. The bootloader copies the compressed
38 data files, to be stored in a read-only filesystem image. Replacing read-only
44 Specifically data ephemeral to the current boot is stored in /run and most
45 application data is stored under /var. Some information continues to be stored
56 for the BMC can be stored in the U-Boot environment, and an init script can
64 information is given for each filesystem such as how the filesystem is stored on
72 The majority of the filesystem is stored in a read-only squashfs in an MTD
99 The majority of the filesystem is stored in a read-only squashfs in a static UBI
107 The environment for Das U-boot continues to be stored at fixed sectors in the
118 supports this feature. For this support, a copy of each kernel is stored on each
|
| /openbmc/linux/fs/nls/ |
| H A D | Kconfig | 44 native language character sets. These character sets are stored
56 native language character sets. These character sets are stored
68 native language character sets. These character sets are stored
81 native language character sets. These character sets are stored in
97 native language character sets. These character sets are stored in
112 native language character sets. These character sets are stored in
123 native language character sets. These character sets are stored in
134 native language character sets. These character sets are stored in
145 native language character sets. These character sets are stored in
156 native language character sets. These character sets are stored in
[all …]
|
| /openbmc/linux/Documentation/fb/ |
| H A D | api.rst | 46 Pixels are stored in memory in hardware-dependent formats. Applications need
51 additional information, which are stored in the variable screen information
55 macropixels. Types describe how macropixels are stored in memory. The following
60 Macropixels are stored contiguously in a single plane. If the number of bits
83 belonging to different planes, is stored in the fixed screen information
88 Macropixels are stored in memory as described by the format FOURCC identifier
89 stored in the variable screen information grayscale field.
93 Pixels are black or white and stored on a number of bits (typically one)
104 Pixels are black or white and stored on a number of bits (typically one)
119 Each component is stored in a macropixel according to the variable screen
[all …]
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | command_syntax_extensions.txt | 88 Ad. 9. Similar to case 2: boot kernel stored in <subimg1> from the image at
96 Ad. 11. Equivalent to case 5: boot kernel stored in <subimg1> from the image
101 Ad. 12. Equivalent to case 6: boot kernel stored in <subimg1> from the image
110 Ad. 14. Equivalent to case 7: boot kernel stored in <subimg1> from the image
141 - boot kernel "kernel-1" stored in a new uImage located at 200000:
152 some other new uImage stored at address 800000:
156 "fdt-1", both stored in some other new uImage located at 800000:
159 - boot kernel "kernel-2" with initrd "ramdisk-2", both stored in a new uImage
160 at address 200000, with a raw FDT blob stored at address 600000:
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | i2c_capture_bytes.md | 5 Captures device register bytes to be stored in an error log.
9 error log, the captured bytes will be stored in the error log.
19 The bytes will be stored in the error log in the same order as they are received
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-inzi.rst | 22 The first plane - Infrared data - is stored according to
24 Each pixel is 16-bit cell, with actual data stored in the 10 LSBs
34 Each cell is a 16-bit word with more significant data stored at higher
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/ |
| H A D | 0006-Platform-CS1000-Increase-buffers-for-EFI-vars.patch | 6 The UEFI variables are stored in the Protected Storage. The size of
28 /* The maximum size of asset to be stored in the Internal Trusted Storage area. */
31 +/* The maximum asset size to be stored in the Protected Storage */
|
| /openbmc/u-boot/board/toradex/common/ |
| H A D | Kconfig | 8 The Toradex config block stored production data on the on-module
52 device the config block is stored on.
59 within the flash device the config block is stored on.
|
| /openbmc/linux/arch/arm/nwfpe/ |
| H A D | softfloat-macros | 39 The result is stored in the location pointed to by `zPtr'.
64 The result is stored in the location pointed to by `zPtr'.
89 64 nonzero bits; this is stored at the location pointed to by `z0Ptr'. The
93 bits shifted off were all zero. This extra result is stored in the location
138 which are stored at the locations pointed to by `z0Ptr' and `z1Ptr'.
173 nonzero. The result is broken into two 64-bit pieces which are stored at
214 stored at the locations pointed to by `z0Ptr' and `z1Ptr'. The bits shifted
218 were all zero. This extra result is stored in the location pointed to by
285 pieces which are stored at the locations pointed to by `z0Ptr' and `z1Ptr'.
304 64-bit pieces which are stored at the locations pointed to by `z0Ptr',
[all …]
|
| /openbmc/u-boot/doc/imx/common/ |
| H A D | imx6.txt | 9 1.1 MAC Address: It is stored in fuse bank 4, with the 32 lsbs in word 2 and the
12 is stored in fuse bank 4, with the 16 lsb in word 3[31:16] and the 32 msbs in
19 - The MAC address is stored in two fuse addresses (the fuse addresses are
|
| /openbmc/docs/designs/ |
| H A D | binarystore-via-blobs.md | 30 - It is not a key store. Because the data stored is accessible to IPMI users and
33 - The data to be stored should not be too large. Since each IPMI packet is
43 Under the hood, the binary blobs are stored as a binary
101 The data is stored as a binary protobuf containing a variable number of binary
133 string with a matching prefix. If there is not already a valid binary stored
141 NOTE: the newly created blob is not serialized and stored until `BmcBlobCommit`
185 blob with binary data stored, BMC handler only populates the `base_id` per
222 **_Host compatibility_**: If data has been stored using IPMI blob binary store,
|