/openbmc/linux/Documentation/filesystems/nfs/ |
H A D | reexport.rst | 36 If the original server uses an X byte filehandle for a given object, the 88 As you can see, the 128-byte NFSv4 filehandle is large enough that
|
/openbmc/linux/Documentation/devicetree/bindings/display/msm/ |
H A D | qcom,sm8250-mdss.yaml | 187 clock-names = "byte", 277 clock-names = "byte",
|
H A D | qcom,sm8550-mdss.yaml | 196 clock-names = "byte", 285 clock-names = "byte",
|
/openbmc/linux/Documentation/translations/zh_CN/PCI/ |
H A D | pci.rst | 408 你可以使用 `pci_(read|write)_config_(byte|word|dword)` 来访问由 414 `pci_bus_(read|write)_config_(byte|word|dword)` 来访问一个给定的设备和该总
|
/openbmc/linux/Documentation/riscv/ |
H A D | hwprobe.rst | 91 than equivalent byte accesses. Misaligned accesses may be supported 95 than equivalent byte accesses.
|
/openbmc/linux/Documentation/powerpc/ |
H A D | ptrace.rst | 24 an 8-byte alignment restriction for hardware watchpoints. We'd like to avoid 73 #define PPC_BREAKPOINT_CONDITION_BE_ALL 0x00ff0000 /* byte enable bits */
|
/openbmc/linux/arch/x86/lib/ |
H A D | checksum_32.S | 158 # Handle 2-byte-aligned regions 182 movzbl (%esi),%ebx # csumming 1 byte, 2-aligned
|
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
H A D | pmbus_read_sensor.md | 39 …ltage output, such as output current, input voltage, and temperature. Two byte value with an 11-bi… 40 | linear_16 | Linear data format used for values related to voltage output. Two byte (16-bit), unsi…
|
/openbmc/pldm/pldmtool/ |
H A D | pldm_base_cmd.cpp | 129 if (b.byte & (1 << i % 8)) in printPldmTypes() 332 if (b.byte & (1 << i % 8)) in printPldmCommands()
|
/openbmc/linux/arch/arm/boot/dts/aspeed/ |
H A D | aspeed-bmc-ibm-everest.dts | 2822 at25,byte-len = <0x80000>; 2838 at25,byte-len = <0x80000>; 2855 at25,byte-len = <0x80000>; 2872 at25,byte-len = <0x80000>; 3195 at25,byte-len = <0x80000>; 3211 at25,byte-len = <0x80000>; 3228 at25,byte-len = <0x80000>; 3245 at25,byte-len = <0x80000>; 3568 at25,byte-len = <0x80000>; 3584 at25,byte-len = <0x80000>; [all …]
|
/openbmc/u-boot/drivers/ram/rockchip/ |
H A D | sdram_rk3399.c | 586 u32 byte; in override_write_leveling_value() local 600 for (byte = 0; byte < 4; byte++) in override_write_leveling_value() 601 clrsetbits_le32(&denali_phy[63 + (128 * byte)], 0xffff << 16, in override_write_leveling_value()
|
/openbmc/u-boot/lib/ |
H A D | Kconfig | 239 The SHA1 algorithm produces a 160-bit (20-byte) hash value 247 The SHA256 algorithm produces a 256-bit (32-byte) hash value 261 The SHA512 algorithm produces a 512-bit (64-byte) hash value 270 The SHA384 algorithm produces a 384-bit (48-byte) hash value 332 family of byte-oriented compression schemes.
|
/openbmc/linux/Documentation/arch/arm64/ |
H A D | memory-tagging-extension.rst | 19 allocation tag for each 16-byte granule in the physical address space. 197 4-bit tag per byte and correspond to a 16-byte MTE tag granule in the 200 **Note**: If ``addr`` is not aligned to a 16-byte granule, the kernel 247 in a byte. With the tag granule of 16 bytes, a 4K page requires 128
|
/openbmc/linux/arch/sparc/lib/ |
H A D | checksum_32.S | 60 addcc %o1, -1, %g0 ! only one byte remains? 63 b 4f ! only one byte remains 69 4: ldub [%o0], %o5 ! get final byte 321 andcc %o1, 4, %g0 ! dest aligned on 4 or 8 byte boundary? 322 be ccdbl + 4 ! 8 byte aligned, kick ass
|
/openbmc/linux/Documentation/scsi/ |
H A D | st.rst | 75 In variable block mode, the byte count in write() determines the size 77 tape block and returns to the user the data if the read() byte count 81 driver is in multiples of the block size. The write() byte count must 132 byte). The bits defining the mode are below the non-rewind bit. The 277 is to use bigger write() byte counts (e.g., tar -b 64). 376 - aa is the buffer size for fixed block mode in 1024 byte units 377 - bb is the write threshold in 1024 byte units 536 reading blocks shorter than the byte count; set this only 559 the lowermost byte is 0xff. Otherwise the lowermost bit 582 given the number of the sense data byte (the lowest eight [all …]
|
/openbmc/docs/designs/mctp/ |
H A D | mctp-kernel.md | 112 including message type byte and optional message integrity check (IC). 285 The application must provide the message type byte as the first byte of the 288 buffer, and the most-significant bit of the message type byte must be 1. 290 If the first byte of the message does not match the message type value, then the 349 The first byte of the message buffer will contain the message type byte. If an 842 ## Including message-type byte in send/receive buffers 845 and from the kernel in receive syscalls will have the message type byte as the 846 first byte of the buffer. This corresponds to the definition of a MCTP message 850 superficially possible for the kernel to prepend this byte on send, and remove 855 would also need to be appended / stripped in conjunction with the type byte) is
|
/openbmc/linux/arch/arm/nwfpe/ |
H A D | fpa11.inl | 34 /* the sysid byte in the status register is readonly */
|
/openbmc/u-boot/doc/imx/common/ |
H A D | imx5.txt | 28 natural MAC byte order (i.e. MSB first).
|
/openbmc/qemu/linux-user/arm/nwfpe/ |
H A D | fpa11.inl | 33 /* the sysid byte in the status register is readonly */
|
/openbmc/u-boot/doc/ |
H A D | README.fec_mxc | 17 Swaps the bytes order of all words(4 byte units) in the packet.
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | pixfmt-inzi.rst | 35 memory address (byte order is little-endian).
|
H A D | pixfmt-srggb16.rst | 30 Each cell is one byte.
|
/openbmc/phosphor-dbus-interfaces/yaml/org/open_power/Control/ |
H A D | Host.interface.yaml | 20 type: variant[byte]
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/fatcat/fatcat/ |
H A D | 0001-Replace-std-ptr_fun-for-c-17.patch | 18 [1] https://en.cppreference.com/w/cpp/string/byte/isspace#Notes
|
/openbmc/openbmc/poky/meta/recipes-connectivity/avahi/files/ |
H A D | CVE-2023-38470-1.patch | 4 Subject: [PATCH] avahi: Ensure each label is at least one byte long
|