serial167: prepare to push BKL down into drivers

[linux-2.6-omap-h63xx.git] / drivers / block / Kconfig

diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
index a4a311992408f5eda8ab093bebbca107dd04faea..0d1d2133d9bc239fe800a3e64c05ceef6c1e898a 100644 (file)
--- a/drivers/block/Kconfig
+++ b/drivers/block/Kconfig
@@ -6,6 +6,12 @@ menuconfig BLK_DEV
        bool "Block devices"
        depends on BLOCK
        default y
        bool "Block devices"
        depends on BLOCK
        default y

+       ---help---
+         Say Y here to get to see options for various different block device
+         drivers. This option alone does not add any kernel code.
+
+         If you say N, all options in this submenu will be skipped and disabled;
+         only do this if you know what you are doing.

 
 if BLK_DEV
 
 
 if BLK_DEV
 


@@ -38,16 +44,6 @@ config MAC_FLOPPY
          If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
          floppy controller, say Y here. Most commonly found in PowerMacs.
 
          If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
          floppy controller, say Y here. Most commonly found in PowerMacs.
 

-config BLK_DEV_PS2
-       tristate "PS/2 ESDI hard disk support"
-       depends on MCA && MCA_LEGACY && BROKEN
-       help
-         Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
-         hard disk.
-
-         To compile this driver as a module, choose M here: the
-         module will be called ps2esdi.
-

 config AMIGA_Z2RAM
        tristate "Amiga Zorro II ramdisk support"
        depends on ZORRO
 config AMIGA_Z2RAM
        tristate "Amiga Zorro II ramdisk support"
        depends on ZORRO


@@ -62,6 +58,7 @@ config AMIGA_Z2RAM
 config BLK_DEV_XD
        tristate "XT hard disk support"
        depends on ISA && ISA_DMA_API
 config BLK_DEV_XD
        tristate "XT hard disk support"
        depends on ISA && ISA_DMA_API

+       select CHECK_SIGNATURE

        help
          Very old 8 bit hard disk controllers used in the IBM XT computer
          will be supported if you say Y here.
        help
          Very old 8 bit hard disk controllers used in the IBM XT computer
          will be supported if you say Y here.


@@ -98,6 +95,17 @@ config PARIDE
          "MicroSolutions backpack protocol", "DataStor Commuter protocol"
          etc.).
 
          "MicroSolutions backpack protocol", "DataStor Commuter protocol"
          etc.).
 

+config GDROM
+       tristate "SEGA Dreamcast GD-ROM drive"
+       depends on SH_DREAMCAST
+       help
+         A standard SEGA Dreamcast comes with a modified CD ROM drive called a
+         "GD-ROM" by SEGA to signify it is capable of reading special disks
+         with up to 1 GB of data. This drive will also read standard CD ROM
+         disks. Select this option to access any disks in your GD ROM drive.
+         Most users will want to say "Y" here.
+         You can also build this as a module which will be called gdrom.ko
+

 source "drivers/block/paride/Kconfig"
 
 config BLK_CPQ_DA
 source "drivers/block/paride/Kconfig"
 
 config BLK_CPQ_DA


@@ -197,23 +205,6 @@ config BLK_DEV_COW_COMMON
        bool
        default BLK_DEV_UBD
 
        bool
        default BLK_DEV_UBD
 

-config MMAPPER
-       tristate "Example IO memory driver (BROKEN)"
-       depends on UML && BROKEN
-       ---help---
-          The User-Mode Linux port can provide support for IO Memory
-          emulation with this option.  This allows a host file to be
-          specified as an I/O region on the kernel command line. That file
-          will be mapped into UML's kernel address space where a driver can
-          locate it and do whatever it wants with the memory, including
-          providing an interface to it for UML processes to use.
-
-          For more information, see
-          <http://user-mode-linux.sourceforge.net/iomem.html>.
-
-          If you'd like to be able to provide a simulated IO port space for
-          User-Mode Linux processes, say Y.  If unsure, say N.
-

 config BLK_DEV_LOOP
        tristate "Loopback device support"
        ---help---
 config BLK_DEV_LOOP
        tristate "Loopback device support"
        ---help---


@@ -321,7 +312,7 @@ config BLK_DEV_UB
          If unsure, say N.
 
 config BLK_DEV_RAM
          If unsure, say N.
 
 config BLK_DEV_RAM

-       tristate "RAM disk support"
+       tristate "RAM block device support"

        ---help---
          Saying Y here will allow you to use a portion of your RAM memory as
          a block device, so that you can make file systems on it, read and
        ---help---
          Saying Y here will allow you to use a portion of your RAM memory as
          a block device, so that you can make file systems on it, read and


@@ -344,7 +335,7 @@ config BLK_DEV_RAM_COUNT
        default "16"
        depends on BLK_DEV_RAM
        help
        default "16"
        depends on BLK_DEV_RAM
        help

-         The default value is 16 RAM disks. Change this if you know what
+         The default value is 16 RAM disks. Change this if you know what you

          are doing. If you boot from a filesystem that needs to be extracted
          in memory, you will need at least one RAM disk (e.g. root on cramfs).
 
          are doing. If you boot from a filesystem that needs to be extracted
          in memory, you will need at least one RAM disk (e.g. root on cramfs).
 


@@ -354,18 +345,17 @@ config BLK_DEV_RAM_SIZE
        default "4096"
        help
          The default value is 4096 kilobytes. Only change this if you know
        default "4096"
        help
          The default value is 4096 kilobytes. Only change this if you know

-         what are you doing. If you are using IBM S/390, then set this to
-         8192.
+         what you are doing.

 
 

-config BLK_DEV_RAM_BLOCKSIZE
-       int "Default RAM disk block size (bytes)"
+config BLK_DEV_XIP
+       bool "Support XIP filesystems on RAM block device"

        depends on BLK_DEV_RAM
        depends on BLK_DEV_RAM

-       default "1024"
+       default n

        help
        help

-         The default value is 1024 bytes.  PAGE_SIZE is a much more
-         efficient choice however.  The default is kept to ensure initrd
-         setups function - apparently needed by the rd_load_image routine
-         that supposes the filesystem in the image uses a 1024 blocksize.
+         Support XIP filesystems (such as ext2 with XIP support on) on
+         top of block ram device. This will slightly enlarge the kernel, and
+         will prevent RAM block device backing store memory from being
+         allocated from highmem (only a problem for highmem systems).

 
 config CDROM_PKTCDVD
        tristate "Packet writing on CD/DVD media"
 
 config CDROM_PKTCDVD
        tristate "Packet writing on CD/DVD media"


@@ -436,4 +426,11 @@ config XEN_BLKDEV_FRONTEND
          block device driver.  It communicates with a back-end driver
          in another domain which drives the actual block device.
 
          block device driver.  It communicates with a back-end driver
          in another domain which drives the actual block device.
 

+config VIRTIO_BLK
+       tristate "Virtio block driver (EXPERIMENTAL)"
+       depends on EXPERIMENTAL && VIRTIO
+       ---help---
+         This is the virtual block driver for virtio.  It can be used with
+          lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
+

 endif # BLK_DEV
 endif # BLK_DEV