Searched refs:byte (Results 1 – 15 of 15) sorted by relevance
/systemd-251/src/udev/ata_id/ |
D | ata_id.c | 393 uint8_t byte[512]; in main() member 448 if (disk_identify(fd, identify.byte, &is_packet_device) == 0) { in main() 453 disk_identify_fixup_string(identify.byte, 10, 20); /* serial */ in main() 454 disk_identify_fixup_string(identify.byte, 23, 8); /* fwrev */ in main() 455 disk_identify_fixup_string(identify.byte, 27, 40); /* model */ in main() 456 disk_identify_fixup_uint16(identify.byte, 0); /* configuration */ in main() 457 disk_identify_fixup_uint16(identify.byte, 75); /* queue depth */ in main() 458 disk_identify_fixup_uint16(identify.byte, 76); /* SATA capabilities */ in main() 459 disk_identify_fixup_uint16(identify.byte, 82); /* command set supported */ in main() 460 disk_identify_fixup_uint16(identify.byte, 83); /* command set supported */ in main() [all …]
|
/systemd-251/src/basic/ |
D | memory-util.c | 21 bool memeqbyte(uint8_t byte, const void *data, size_t length) { in memeqbyte() argument 34 if (p[i] != byte) in memeqbyte()
|
D | siphash24.h | 24 #define siphash24_compress_byte(byte, state) siphash24_compress((const uint8_t[]) { (byte) }, 1, (s… argument
|
D | memory-util.h | 58 bool memeqbyte(uint8_t byte, const void *data, size_t length);
|
D | virt.c | 224 uint8_t byte = (uint8_t) s[19]; in detect_vm_smbios() local 225 if (byte & (1U<<4)) { in detect_vm_smbios()
|
/systemd-251/src/network/ |
D | networkd-dhcp-common.c | 1151 uint32_t byte; in config_parse_duid_rawdata() local 1185 byte = ((uint8_t) n1 << (4 * (len-1))) | (uint8_t) n2; in config_parse_duid_rawdata() 1186 raw_data[count++] = byte; in config_parse_duid_rawdata()
|
/systemd-251/docs/ |
D | GVARIANT-SERIALIZATION.md | 16 3. Padding with NUL bytes to pad up to next 8byte boundary
|
D | PASSWORD_AGENTS.md | 33 … entry was successful or not. You may but don't have to include a final `NUL` byte in your message.
|
D | JOURNAL_EXPORT_FORMATS.md | 133 …y without losing data, since JSON cannot embed binary data natively. Each byte of the binary field…
|
D | CODING_STYLE.md | 520 actually mean a byte-sized signed or unsigned integers. When referring to a 521 generic byte, we generally prefer the unsigned variant `uint8_t`. Do not use 645 `uint16_t`. Also, "network byte order" is just a weird name for "big endian",
|
D | JOURNAL_NATIVE_PROTOCOL.md | 72 byte. In this case, the key name is serialized as is, followed by a `\n`
|
/systemd-251/ |
D | TODO | 1493 - journal: deal nicely with byte-by-byte copied files, especially regards header
|
D | NEWS | 4439 bits 0–7 in byte 0, CPUs 8–15 are described by byte 1, and so on). 5865 byte threshold value. All journal objects larger than this threshold 6897 traffic accounting (packet count as well as byte count) is done for
|
/systemd-251/hwdb.d/ |
D | 20-OUI.hwdb | 15246 ID_OUI_FROM_DATABASE=Giga-byte Communications Inc.
|
D | ma-large.txt | 99089 00-13-F3 (hex) Giga-byte Communications Inc. 99090 0013F3 (base 16) Giga-byte Communications Inc.
|