Home
last modified time | relevance | path

Searched full:laid (Results 1 – 25 of 153) sorted by relevance

1234567

/openbmc/linux/drivers/md/
H A Draid10.h37 int near_copies; /* number of copies laid out
39 int far_copies; /* number of copies laid out
/openbmc/linux/include/drm/
H A Ddrm_fourcc.h148 * format with data laid in a single plane
162 * format with data laid in two planes (luminance and chrominance)
176 * format with data laid in three planes (one for each YUV component)
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-driver-tegra-fuse6 data programmed at the factory. The data is laid out in 32bit
/openbmc/linux/drivers/net/ethernet/intel/igc/
H A Digc_diag.h16 /* In the hardware, registers are laid out either singly, in arrays
/openbmc/linux/Documentation/scsi/
H A Dsym53c500_cs.rst22 other products using this chip, but I've never laid eyes (much less hands)
/openbmc/u-boot/drivers/video/fonts/
H A DKconfig37 A laid-back handwritten font.
/openbmc/linux/include/linux/
H A Dpacking.h22 * format. Unpacked means laid out in memory in the CPU's native
H A Dlitex.h30 * 32-bit wide logical CSR will be laid out as four 32-bit physical
H A Dpage-flags-layout.h40 * There are five possibilities for how page->flags get laid out. The first
/openbmc/linux/tools/testing/selftests/arm64/signal/
H A Dsignals.S48 * For simplicity this assumes that current field 'token' is laid out
/openbmc/u-boot/doc/device-tree-bindings/video/
H A Drockchip-lvds.txt16 This describes how the color bits are laid out in the
/openbmc/linux/arch/sparc/include/uapi/asm/
H A Dpsr.h15 /* The Sparc PSR fields are laid out as the following:
/openbmc/linux/include/uapi/rdma/
H A Dcxgb4-abi.h41 * Make sure that all structs defined in this file remain laid out so
H A Dmthca-abi.h47 * Make sure that all structs defined in this file remain laid out so
H A Dmlx4-abi.h49 * Make sure that all structs defined in this file remain laid out so
/openbmc/u-boot/arch/arm/include/asm/ti-common/
H A Dti-edma3.h58 /* PaRAM slots are laid out like this */
/openbmc/linux/arch/openrisc/include/asm/
H A Dptrace.h31 * This struct describes how the registers are laid out on the kernel stack
/openbmc/linux/arch/arm64/xen/
H A Dhypercall.S46 * Parameter structs passed to hypercalls are laid out according to
/openbmc/linux/Documentation/block/
H A Ddeadline-iosched.rst63 or a front merge candidate. Due to the way files are typically laid out,
/openbmc/linux/include/asm-generic/
H A Diomap.h78 * want MMIO that copies stuff laid out in MMIO
/openbmc/qemu/include/tcg/
H A Dtcg-cond.h29 * Conditions. Note that these are laid out for easy manipulation by
/openbmc/linux/arch/m68k/mac/
H A Doss.c96 * This IRQ mapping is laid out with two things in mind: first, we try to keep
/openbmc/linux/include/uapi/linux/
H A Dvirtio_balloon.h95 * NOTE: fields are laid out in a way that would make compiler add padding
/openbmc/qemu/include/standard-headers/linux/
H A Dvirtio_balloon.h107 * NOTE: fields are laid out in a way that would make compiler add padding
/openbmc/linux/Documentation/filesystems/ext4/
H A Dgroup_descr.rst43 The block group descriptor is laid out in ``struct ext4_group_desc``.

1234567