Lines Matching +full:40 +full:a

10 One can memory-map a pointer to a carefully crafted struct over the hardware
20 A more robust alternative to struct field definitions would be to extract the
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.
47 The following examples cover the memory layout of a packed u64 field.
55   63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
71   56 57 58 59 60 61 62 63 48 49 50 51 52 53 54 55 40 41 42 43 44 45 46 47 32 33 34 35 36 37 38 39
77 inverts bit offsets inside a byte.
84   39 38 37 36 35 34 33 32 47 46 45 44 43 42 41 40 55 54 53 52 51 50 49 48 63 62 61 60 59 58 57 56
98   32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
110   63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
125   56 57 58 59 60 61 62 63 48 49 50 51 52 53 54 55 40 41 42 43 44 45 46 47 32 33 34 35 36 37 38 39
136   39 38 37 36 35 34 33 32 47 46 45 44 43 42 41 40 55 54 53 52 51 50 49 48 63 62 61 60 59 58 57 56
147   32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
169 Example with a 31 byte sized buffer given below. Physical buffer offsets are
170 implicit, and increase from left to right within a group, and from top to
171 bottom within a column.
229 quirk combinations (for a total of 8) match what the hardware documentation
241 during runtime, therefore it is reasonable to wrap packing() into a custom
285 fields represented in a buffer, and it encourages consumer drivers to avoid
302 It is recommended, but not required, that you wrap your packed buffer into a
303 structured type with a fixed size. This generally makes it easier for the