Lines Matching +full:cpu +full:- +full:offset

6 -----------------
10 One can memory-map a pointer to a carefully crafted struct over the hardware
13 due to potential endianness mismatches between the CPU and the hardware device.
23 were performed byte-by-byte. Also the code can easily get cluttered, and the
24 high-level idea might get lost among the many bit shifts required.
25 Many drivers take the bit-shifting approach and then attempt to reduce the
30 ------------
34   - Packing a CPU-usable number into a memory buffer (with hardware
36   - Unpacking a memory buffer (which has hardware constraints/quirks)
37     into a CPU-usable number.
40 over CPU endianness and therefore between possible mismatches between
43 The basic unit of these API functions is the u64. From the CPU's
44 perspective, bit 63 always means bit offset 7 of byte 7, albeit only
60 That is, the MSByte (7) of the CPU-usable u64 sits at memory offset 0, and the
61 LSByte (0) of the u64 sits at memory offset 7.
90 byte from each 4-byte word is placed at its mirrored position compared to
114 4 bytes correspond to the least significant 4-byte word, next 4 bytes to
115 the more significant 4-byte word.
155 ------------
160 xxx_packing() that calls it using the proper QUIRK_* one-hot bits set.
162 The packing() function returns an int-encoded error code, which protects the