Searched full:laid (Results 1 – 25 of 200) sorted by relevance
12345678
37 int near_copies; /* number of copies laid out39 int far_copies; /* number of copies laid out
148 * format with data laid in a single plane162 * format with data laid in two planes (luminance and chrominance)176 * format with data laid in three planes (one for each YUV component)
16 /* In the hardware, registers are laid out either singly, in arrays
16 other products using this chip, but I've never laid eyes (much less hands)
22 other products using this chip, but I've never laid eyes (much less hands)
227 * in row-major layout. Within the tile bytes are laid out row-major, with241 * in row-major layout. Within the tile bytes are laid out in OWORD (16 bytes)256 * Within the tile pixels are laid out in 16 256 byte units / sub-tiles which258 * Each group therefore consits out of four 256 byte units, which are also laid290 * Macroblocks are laid in a Z-shape, and each pixel data is following the370 * Within a GOB, data is ordered as 16B x 2 lines sectors laid in Z-shape.
48 * For simplicity this assumes that current field 'token' is laid out
22 * format. Unpacked means laid out in memory in the CPU's native
39 * There are five possibilities for how page->flags get laid out. The first
41 * Make sure that all structs defined in this file remain laid out so
47 * Make sure that all structs defined in this file remain laid out so
15 /* The Sparc PSR fields are laid out as the following:
38 * There are five possibilities for how page->flags get laid out. The first
35 * This struct describes how the registers are laid out on the kernel stack
31 * This struct describes how the registers are laid out on the kernel stack
64 or a front merge candidate. Due to the way files are typically laid out,
50 accessed via an ioport) and laid out with a direct correspondence to the
56 * want MMIO that copies stuff laid out in MMIO
46 * Parameter structs passed to hypercalls are laid out according to