Home
last modified time | relevance | path

Searched refs:Block (Results 201 – 225 of 340) sorted by relevance

12345678910>>...14

/openbmc/linux/Documentation/networking/device_drivers/ethernet/google/
H A Dgve.rst112 Notification Block Interrupts
/openbmc/linux/Documentation/filesystems/ext4/
H A Difork.rst18 Direct/Indirect Block Addressing
H A Dinodes.rst112 - Block map or extent tree. See the section “The Contents of inode.i_block”.
218 - S_IFBLK (Block device)
/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Drenesas,rsnd.txt104 - CMD Block
/openbmc/linux/arch/arm/boot/dts/broadcom/
H A Dbcm-ns.dtsi101 /* Switch Register Access Block */
/openbmc/qemu/docs/interop/
H A Dlive-block-operations.rst7 .. _Live Block Operations:
10 Live Block Device Operations
13 QEMU Block Layer currently (as of QEMU 2.9) supports four major kinds of
661 and QEMU's built-in Network Block Device (NBD) server. Here's a quick
989 The ``blockdev-backup`` command operates at node-level in a Block Driver
H A Dparallels.txt29 BAT Block Allocation Table, an entity that contains information for
/openbmc/linux/drivers/md/
H A DKconfig3 # Block device driver configuration
253 bool "Block manager locking"
256 Block manager locking can catch various metadata corruption issues.
/openbmc/u-boot/arch/x86/include/asm/acpi/
H A Dirqlinks.asl16 * Block (ILB) memory space.
/openbmc/linux/drivers/char/ipmi/
H A DKconfig186 Provides a driver for the BT (Block Transfer) IPMI interface
/openbmc/linux/Documentation/devicetree/bindings/interconnect/
H A Dsamsung,exynos-bus.yaml76 |Block|LEFTBUS|RIGHTBUS|MCUISP |ISP |PERIL ||VDD_INT |
/openbmc/linux/Documentation/powerpc/
H A Delf_hwcaps.rst139 User's Manual, 4.6.2.2 Instruction Cache Block Invalidate (icbi))::
/openbmc/linux/Documentation/admin-guide/media/
H A Dvivid.rst526 The FM receiver supports RDS as well, both using 'Block I/O' and 'Controls'
529 or when the tuner status is requested. The Block I/O method uses the read()
558 The FM transmitter supports RDS as well, both using 'Block I/O' and 'Controls'
560 using controls, and in 'Block I/O' mode the blocks are passed to the driver
1045 "Block I/O", then they are inactive as well. If RDS Rx I/O Mode is set
1073 this can be "Block I/O" where the RDS blocks have to be read()
1118 this can be "Block I/O" where the application has to use write()
/openbmc/u-boot/doc/
H A DREADME.coccinelle407 /* Block size must be >= 4 bytes. */
451 /* Block size must be >= 4 bytes. */
/openbmc/qemu/docs/
H A Dqdev-device-use.txt28 === Block Devices ===
350 * disk:... See "Block Devices"
H A Dcolo-proxy.txt214 a.COLO-proxy must work with COLO-frame and Block-replication.
/openbmc/intel-ipmi-oem/
H A Dipmi-allowlist.conf330 0x3e:0x35:0xff7f //<Intel Managed Data Region>:<MDR2 Dget Data Block>
336 0x3e:0x3d:0x7f7f //<Intel Managed Data Region>:<MDR2 Data Block>
/openbmc/linux/drivers/block/
H A DKconfig3 # Block device driver configuration
7 bool "Block devices"
/openbmc/u-boot/board/freescale/t4qds/
H A DREADME180 Block #blocks Definition Size
/openbmc/qemu/docs/system/
H A Ddevice-url-syntax.rst.inc47 QEMU supports NBD (Network Block Devices) both using TCP protocol as
H A Dintroduction.rst50 There is a full :ref:`featured block layer<Live Block Operations>`
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/uefi/files/n1sdp/
H A D0005-Platform-ARM-N1Sdp-NOR-flash-Dxe-Driver-for-N1Sdp.patch628 + @param[in] BlockSize Block size of NOR flash device.
797 + @param[in] BlockAddress Block address within the variable region.
840 + @param[in] BlockAddress Block address within the variable store region.
871 + "EraseSingleBlock(BlockAddress=0x%08x: Block Locked Error (try to erase %d times)\n",
1562 + @param[in] BlockSize Block size of NOR flash device.
1831 + @param[in] BlockAddress Block address within the variable store region.
/openbmc/u-boot/board/keymile/km_arm/
H A Dkwbimage_256M8_1.cfg250 # bit 15: 1, Use ODT Block
H A Dkwbimage_128M16_1.cfg250 # bit 15: 1, Use ODT Block
/openbmc/qemu/docs/devel/
H A Dmultiple-iothreads.txt123 Block layer code must therefore expect to run in an IOThread and avoid using

12345678910>>...14