/openbmc/linux/drivers/i2c/busses/ |
H A D | i2c-highlander.c | 293 dev->buf = &data->byte; in highlander_i2c_smbus_xfer()
|
/openbmc/linux/fs/ntfs/ |
H A D | mft.c | 1132 u8 *buf, *byte; in ntfs_mft_bitmap_find_and_alloc_free_rec_nolock() local 1202 byte = buf + (bit >> 3); in ntfs_mft_bitmap_find_and_alloc_free_rec_nolock() 1203 if (*byte == 0xff) in ntfs_mft_bitmap_find_and_alloc_free_rec_nolock() 1205 b = ffz((unsigned long)*byte); in ntfs_mft_bitmap_find_and_alloc_free_rec_nolock() 1212 *byte |= 1 << b; in ntfs_mft_bitmap_find_and_alloc_free_rec_nolock()
|
/openbmc/linux/Documentation/bpf/ |
H A D | verifier.rst | 165 mask and value; no bit should ever be 1 in both. For example, if a byte is read 194 is 2 bytes after a 4-byte alignment. If a program adds 14 bytes to that to jump 197 bytes (NET_IP_ALIGN) gives a 4-byte alignment and so word-sized accesses through 222 this 2byte load from the packet is safe to do, since the program author 239 6: r0 = *(u8 *)(r3 +7) /* load 7th byte from the packet */
|
/openbmc/u-boot/doc/uImage.FIT/ |
H A D | source_file_format.txt | 287 store is placed immediately after the last byte of the device tree binary, 288 aligned to a 4-byte boundary.
|
/openbmc/u-boot/doc/driver-model/ |
H A D | of-plat.txt | 44 are wrong in several fairly common cases. For example an 8-byte value 45 is considered to be a 2-item integer array, and is byte-swapped. A
|
/openbmc/intel-ipmi-oem/docs/ |
H A D | Intel_IPMI_Platform_Events.md | 268 // > Use a function to log specified byte of payload as Parameter 269 // in chosen format. Here it stores 2-nd byte in hex format.
|
/openbmc/linux/Documentation/netlink/ |
H A D | netlink-raw.yaml | 127 byte-order: 210 byte-order:
|
/openbmc/linux/drivers/mmc/host/ |
H A D | mmc_spi.c | 158 unsigned n, u8 byte) in mmc_spi_skip() argument 172 if (cp[i] != byte) in mmc_spi_skip()
|
/openbmc/linux/drivers/edac/ |
H A D | i5100_edac.c | 700 u8 ch, u8 slot, u8 addr, u8 *byte) in i5100_read_spd_byte() argument 725 *byte = i5100_spddata_data(w); in i5100_read_spd_byte()
|
/openbmc/linux/Documentation/wmi/devices/ |
H A D | dell-wmi-ddv.rst | 205 Returns a single block of analytics data, with the second byte 242 TODO: Find out what the meaning of the last byte is.
|
/openbmc/u-boot/common/ |
H A D | dlmalloc.src | 72 Alignment: 8-byte 73 8 byte alignment is currently hardwired into the design. This 77 Code for 8-byte pointers is untested by me but has worked 88 Minimum allocated size: 4-byte ptrs: 16 bytes (including 4 overhead) 89 8-byte ptrs: 24/32 bytes (including, 4/8 overhead) 91 When a chunk is freed, 12 (for 4byte ptrs) or 20 (for 8 byte 92 ptrs but 4 byte size) or 24 (for 8/8) additional bytes are 100 Maximum allocated size: 4-byte size_t: 2^31 - 8 bytes 101 8-byte size_t: 2^63 - 16 bytes 2047 obtain 8-byte alignment and/or to obtain a size of at least [all …]
|
/openbmc/qemu/dump/ |
H A D | dump.c | 1208 uint32_t byte, bit; in set_dump_bitmap() local 1245 byte = (pfn % bits_per_buf) / CHAR_BIT; in set_dump_bitmap() 1248 buf[byte] |= 1u << bit; in set_dump_bitmap() 1250 buf[byte] &= ~(1u << bit); in set_dump_bitmap()
|
/openbmc/linux/Documentation/networking/ |
H A D | timestamping.rst | 182 sockets, it increments with every byte. For stream sockets, also set 218 write_seq is the last byte written by the process. This offset is 326 byte range can coexist in multiple segments for protocols that 349 individual last byte passed to send(), even if it is no longer the 350 last byte after an skbuff extend or merge operation. It stores the 356 enabling SOF_TIMESTAMPING_OPT_ID and comparing the byte offset at
|
/openbmc/linux/Documentation/admin-guide/cifs/ |
H A D | usage.rst | 380 4096 byte pages) 580 Do not send byte range lock requests to the server. 582 with cifs style mandatory byte range locks (and most 584 byte range locks). 586 Even if the server supports posix (advisory) byte range 589 DOS/Windows, which require Windows style mandatory byte range 811 than one second to complete (except for byte range lock requests).
|
/openbmc/linux/Documentation/scsi/ |
H A D | 53c700.rst | 134 Disable 8 byte bursting for DMA transfers.
|
/openbmc/linux/Documentation/hwmon/ |
H A D | occ.rst | 148 This is one byte hexadecimal value. Bit 7 indicates the
|
/openbmc/u-boot/doc/ |
H A D | README.android-fastboot-protocol | 102 for illustration only here) and without a trailing 0 byte.
|
/openbmc/linux/Documentation/translations/it_IT/process/ |
H A D | submit-checklist.rst | 66 che usa più di 512 byte sullo stack è una buona candidata per una
|
/openbmc/qemu/target/arm/tcg/ |
H A D | t16.decode | 84 # Load/store word/byte (immediate offset)
|
/openbmc/linux/Documentation/driver-api/tty/ |
H A D | n_gsm.rst | 115 for the second time. The byte sequence for the disconnect command frame is::
|
/openbmc/linux/drivers/net/ethernet/dec/tulip/ |
H A D | Kconfig | 37 own cache lines. Value of 4 corresponds to the typical 32 byte line
|
/openbmc/linux/Documentation/devicetree/bindings/display/msm/ |
H A D | qcom,sc7280-mdss.yaml | 183 clock-names = "byte",
|
/openbmc/linux/Documentation/driver-api/media/drivers/ |
H A D | pxa_camera.rst | 13 This is due to DMA constraints, which transfers only planes of 8 byte
|
/openbmc/linux/Documentation/translations/zh_CN/dev-tools/ |
H A D | kasan.rst | 193 128-byte region [ffff8801f44ec300, ffff8801f44ec380)
|
/openbmc/pldm/libpldmresponder/ |
H A D | platform.hpp | 400 !(states->states[bitfieldIndex].byte & (1 << bit))) in setStateEffecterStatesHandler()
|