Root/drivers/block/Kconfig

1#
2# Block device driver configuration
3#
4
5menuconfig BLK_DEV
6    bool "Block devices"
7    depends on BLOCK
8    default y
9    ---help---
10      Say Y here to get to see options for various different block device
11      drivers. This option alone does not add any kernel code.
12
13      If you say N, all options in this submenu will be skipped and disabled;
14      only do this if you know what you are doing.
15
16if BLK_DEV
17
18config BLK_DEV_FD
19    tristate "Normal floppy disk support"
20    depends on ARCH_MAY_HAVE_PC_FDC
21    ---help---
22      If you want to use the floppy disk drive(s) of your PC under Linux,
23      say Y. Information about this driver, especially important for IBM
24      Thinkpad users, is contained in
25      <file:Documentation/blockdev/floppy.txt>.
26      That file also contains the location of the Floppy driver FAQ as
27      well as location of the fdutils package used to configure additional
28      parameters of the driver at run time.
29
30      To compile this driver as a module, choose M here: the
31      module will be called floppy.
32
33config AMIGA_FLOPPY
34    tristate "Amiga floppy support"
35    depends on AMIGA
36
37config ATARI_FLOPPY
38    tristate "Atari floppy support"
39    depends on ATARI
40
41config MAC_FLOPPY
42    tristate "Support for PowerMac floppy"
43    depends on PPC_PMAC && !PPC_PMAC64
44    help
45      If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
46      floppy controller, say Y here. Most commonly found in PowerMacs.
47
48config BLK_DEV_SWIM
49    tristate "Support for SWIM Macintosh floppy"
50    depends on M68K && MAC
51    help
52      You should select this option if you want floppy support
53      and you don't have a II, IIfx, Q900, Q950 or AV series.
54
55config AMIGA_Z2RAM
56    tristate "Amiga Zorro II ramdisk support"
57    depends on ZORRO
58    help
59      This enables support for using Chip RAM and Zorro II RAM as a
60      ramdisk or as a swap partition. Say Y if you want to include this
61      driver in the kernel.
62
63      To compile this driver as a module, choose M here: the
64      module will be called z2ram.
65
66config GDROM
67    tristate "SEGA Dreamcast GD-ROM drive"
68    depends on SH_DREAMCAST
69    help
70      A standard SEGA Dreamcast comes with a modified CD ROM drive called a
71      "GD-ROM" by SEGA to signify it is capable of reading special disks
72      with up to 1 GB of data. This drive will also read standard CD ROM
73      disks. Select this option to access any disks in your GD ROM drive.
74      Most users will want to say "Y" here.
75      You can also build this as a module which will be called gdrom.
76
77config PARIDE
78    tristate "Parallel port IDE device support"
79    depends on PARPORT_PC
80    ---help---
81      There are many external CD-ROM and disk devices that connect through
82      your computer's parallel port. Most of them are actually IDE devices
83      using a parallel port IDE adapter. This option enables the PARIDE
84      subsystem which contains drivers for many of these external drives.
85      Read <file:Documentation/blockdev/paride.txt> for more information.
86
87      If you have said Y to the "Parallel-port support" configuration
88      option, you may share a single port between your printer and other
89      parallel port devices. Answer Y to build PARIDE support into your
90      kernel, or M if you would like to build it as a loadable module. If
91      your parallel port support is in a loadable module, you must build
92      PARIDE as a module. If you built PARIDE support into your kernel,
93      you may still build the individual protocol modules and high-level
94      drivers as loadable modules. If you build this support as a module,
95      it will be called paride.
96
97      To use the PARIDE support, you must say Y or M here and also to at
98      least one high-level driver (e.g. "Parallel port IDE disks",
99      "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
100      to at least one protocol driver (e.g. "ATEN EH-100 protocol",
101      "MicroSolutions backpack protocol", "DataStor Commuter protocol"
102      etc.).
103
104source "drivers/block/paride/Kconfig"
105
106source "drivers/block/mtip32xx/Kconfig"
107
108config BLK_CPQ_DA
109    tristate "Compaq SMART2 support"
110    depends on PCI && VIRT_TO_BUS
111    help
112      This is the driver for Compaq Smart Array controllers. Everyone
113      using these boards should say Y here. See the file
114      <file:Documentation/blockdev/cpqarray.txt> for the current list of
115      boards supported by this driver, and for further information on the
116      use of this driver.
117
118config BLK_CPQ_CISS_DA
119    tristate "Compaq Smart Array 5xxx support"
120    depends on PCI
121    select CHECK_SIGNATURE
122    help
123      This is the driver for Compaq Smart Array 5xxx controllers.
124      Everyone using these boards should say Y here.
125      See <file:Documentation/blockdev/cciss.txt> for the current list of
126      boards supported by this driver, and for further information
127      on the use of this driver.
128
129config CISS_SCSI_TAPE
130    bool "SCSI tape drive support for Smart Array 5xxx"
131    depends on BLK_CPQ_CISS_DA && PROC_FS
132    depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
133    help
134      When enabled (Y), this option allows SCSI tape drives and SCSI medium
135      changers (tape robots) to be accessed via a Compaq 5xxx array
136      controller. (See <file:Documentation/blockdev/cciss.txt> for more details.)
137
138      "SCSI support" and "SCSI tape support" must also be enabled for this
139      option to work.
140
141      When this option is disabled (N), the SCSI portion of the driver
142      is not compiled.
143
144config BLK_DEV_DAC960
145    tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
146    depends on PCI
147    help
148      This driver adds support for the Mylex DAC960, AcceleRAID, and
149      eXtremeRAID PCI RAID controllers. See the file
150      <file:Documentation/blockdev/README.DAC960> for further information
151      about this driver.
152
153      To compile this driver as a module, choose M here: the
154      module will be called DAC960.
155
156config BLK_DEV_UMEM
157    tristate "Micro Memory MM5415 Battery Backed RAM support"
158    depends on PCI
159    ---help---
160      Saying Y here will include support for the MM5415 family of
161      battery backed (Non-volatile) RAM cards.
162      <http://www.umem.com/>
163
164      The cards appear as block devices that can be partitioned into
165      as many as 15 partitions.
166
167      To compile this driver as a module, choose M here: the
168      module will be called umem.
169
170      The umem driver has not yet been allocated a MAJOR number, so
171      one is chosen dynamically.
172
173config BLK_DEV_UBD
174    bool "Virtual block device"
175    depends on UML
176    ---help---
177          The User-Mode Linux port includes a driver called UBD which will let
178          you access arbitrary files on the host computer as block devices.
179          Unless you know that you do not need such virtual block devices say
180          Y here.
181
182config BLK_DEV_UBD_SYNC
183    bool "Always do synchronous disk IO for UBD"
184    depends on BLK_DEV_UBD
185    ---help---
186      Writes to the virtual block device are not immediately written to the
187      host's disk; this may cause problems if, for example, the User-Mode
188      Linux 'Virtual Machine' uses a journalling filesystem and the host
189      computer crashes.
190
191          Synchronous operation (i.e. always writing data to the host's disk
192          immediately) is configurable on a per-UBD basis by using a special
193          kernel command line option. Alternatively, you can say Y here to
194          turn on synchronous operation by default for all block devices.
195
196          If you're running a journalling file system (like reiserfs, for
197          example) in your virtual machine, you will want to say Y here. If
198          you care for the safety of the data in your virtual machine, Y is a
199          wise choice too. In all other cases (for example, if you're just
200          playing around with User-Mode Linux) you can choose N.
201
202config BLK_DEV_COW_COMMON
203    bool
204    default BLK_DEV_UBD
205
206config BLK_DEV_LOOP
207    tristate "Loopback device support"
208    ---help---
209      Saying Y here will allow you to use a regular file as a block
210      device; you can then create a file system on that block device and
211      mount it just as you would mount other block devices such as hard
212      drive partitions, CD-ROM drives or floppy drives. The loop devices
213      are block special device files with major number 7 and typically
214      called /dev/loop0, /dev/loop1 etc.
215
216      This is useful if you want to check an ISO 9660 file system before
217      burning the CD, or if you want to use floppy images without first
218      writing them to floppy. Furthermore, some Linux distributions avoid
219      the need for a dedicated Linux partition by keeping their complete
220      root file system inside a DOS FAT file using this loop device
221      driver.
222
223      To use the loop device, you need the losetup utility, found in the
224      util-linux package, see
225      <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
226
227      The loop device driver can also be used to "hide" a file system in
228      a disk partition, floppy, or regular file, either using encryption
229      (scrambling the data) or steganography (hiding the data in the low
230      bits of, say, a sound file). This is also safe if the file resides
231      on a remote file server.
232
233      There are several ways of encrypting disks. Some of these require
234      kernel patches. The vanilla kernel offers the cryptoloop option
235      and a Device Mapper target (which is superior, as it supports all
236      file systems). If you want to use the cryptoloop, say Y to both
237      LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
238      or later) version of util-linux. Additionally, be aware that
239      the cryptoloop is not safe for storing journaled filesystems.
240
241      Note that this loop device has nothing to do with the loopback
242      device used for network connections from the machine to itself.
243
244      To compile this driver as a module, choose M here: the
245      module will be called loop.
246
247      Most users will answer N here.
248
249config BLK_DEV_LOOP_MIN_COUNT
250    int "Number of loop devices to pre-create at init time"
251    depends on BLK_DEV_LOOP
252    default 8
253    help
254      Static number of loop devices to be unconditionally pre-created
255      at init time.
256
257      This default value can be overwritten on the kernel command
258      line or with module-parameter loop.max_loop.
259
260      The historic default is 8. If a late 2011 version of losetup(8)
261      is used, it can be set to 0, since needed loop devices can be
262      dynamically allocated with the /dev/loop-control interface.
263
264config BLK_DEV_CRYPTOLOOP
265    tristate "Cryptoloop Support"
266    select CRYPTO
267    select CRYPTO_CBC
268    depends on BLK_DEV_LOOP
269    ---help---
270      Say Y here if you want to be able to use the ciphers that are
271      provided by the CryptoAPI as loop transformation. This might be
272      used as hard disk encryption.
273
274      WARNING: This device is not safe for journaled file systems like
275      ext3 or Reiserfs. Please use the Device Mapper crypto module
276      instead, which can be configured to be on-disk compatible with the
277      cryptoloop device.
278
279source "drivers/block/drbd/Kconfig"
280
281config BLK_DEV_NBD
282    tristate "Network block device support"
283    depends on NET
284    ---help---
285      Saying Y here will allow your computer to be a client for network
286      block devices, i.e. it will be able to use block devices exported by
287      servers (mount file systems on them etc.). Communication between
288      client and server works over TCP/IP networking, but to the client
289      program this is hidden: it looks like a regular local file access to
290      a block device special file such as /dev/nd0.
291
292      Network block devices also allows you to run a block-device in
293      userland (making server and client physically the same computer,
294      communicating using the loopback network device).
295
296      Read <file:Documentation/blockdev/nbd.txt> for more information,
297      especially about where to find the server code, which runs in user
298      space and does not need special kernel support.
299
300      Note that this has nothing to do with the network file systems NFS
301      or Coda; you can say N here even if you intend to use NFS or Coda.
302
303      To compile this driver as a module, choose M here: the
304      module will be called nbd.
305
306      If unsure, say N.
307
308config BLK_DEV_NVME
309    tristate "NVM Express block device"
310    depends on PCI
311    ---help---
312      The NVM Express driver is for solid state drives directly
313      connected to the PCI or PCI Express bus. If you know you
314      don't have one of these, it is safe to answer N.
315
316      To compile this driver as a module, choose M here: the
317      module will be called nvme.
318
319config BLK_DEV_OSD
320    tristate "OSD object-as-blkdev support"
321    depends on SCSI_OSD_ULD
322    ---help---
323      Saying Y or M here will allow the exporting of a single SCSI
324      OSD (object-based storage) object as a Linux block device.
325
326      For example, if you create a 2G object on an OSD device,
327      you can then use this module to present that 2G object as
328      a Linux block device.
329
330      To compile this driver as a module, choose M here: the
331      module will be called osdblk.
332
333      If unsure, say N.
334
335config BLK_DEV_SX8
336    tristate "Promise SATA SX8 support"
337    depends on PCI
338    ---help---
339      Saying Y or M here will enable support for the
340      Promise SATA SX8 controllers.
341
342      Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
343
344config BLK_DEV_RAM
345    tristate "RAM block device support"
346    ---help---
347      Saying Y here will allow you to use a portion of your RAM memory as
348      a block device, so that you can make file systems on it, read and
349      write to it and do all the other things that you can do with normal
350      block devices (such as hard drives). It is usually used to load and
351      store a copy of a minimal root file system off of a floppy into RAM
352      during the initial install of Linux.
353
354      Note that the kernel command line option "ramdisk=XX" is now obsolete.
355      For details, read <file:Documentation/blockdev/ramdisk.txt>.
356
357      To compile this driver as a module, choose M here: the
358      module will be called rd.
359
360      Most normal users won't need the RAM disk functionality, and can
361      thus say N here.
362
363config BLK_DEV_RAM_COUNT
364    int "Default number of RAM disks"
365    default "16"
366    depends on BLK_DEV_RAM
367    help
368      The default value is 16 RAM disks. Change this if you know what you
369      are doing. If you boot from a filesystem that needs to be extracted
370      in memory, you will need at least one RAM disk (e.g. root on cramfs).
371
372config BLK_DEV_RAM_SIZE
373    int "Default RAM disk size (kbytes)"
374    depends on BLK_DEV_RAM
375    default "4096"
376    help
377      The default value is 4096 kilobytes. Only change this if you know
378      what you are doing.
379
380config BLK_DEV_XIP
381    bool "Support XIP filesystems on RAM block device"
382    depends on BLK_DEV_RAM
383    default n
384    help
385      Support XIP filesystems (such as ext2 with XIP support on) on
386      top of block ram device. This will slightly enlarge the kernel, and
387      will prevent RAM block device backing store memory from being
388      allocated from highmem (only a problem for highmem systems).
389
390config CDROM_PKTCDVD
391    tristate "Packet writing on CD/DVD media"
392    depends on !UML
393    help
394      If you have a CDROM/DVD drive that supports packet writing, say
395      Y to include support. It should work with any MMC/Mt Fuji
396      compliant ATAPI or SCSI drive, which is just about any newer
397      DVD/CD writer.
398
399      Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
400      is possible.
401      DVD-RW disks must be in restricted overwrite mode.
402
403      See the file <file:Documentation/cdrom/packet-writing.txt>
404      for further information on the use of this driver.
405
406      To compile this driver as a module, choose M here: the
407      module will be called pktcdvd.
408
409config CDROM_PKTCDVD_BUFFERS
410    int "Free buffers for data gathering"
411    depends on CDROM_PKTCDVD
412    default "8"
413    help
414      This controls the maximum number of active concurrent packets. More
415      concurrent packets can increase write performance, but also require
416      more memory. Each concurrent packet will require approximately 64Kb
417      of non-swappable kernel memory, memory which will be allocated when
418      a disc is opened for writing.
419
420config CDROM_PKTCDVD_WCACHE
421    bool "Enable write caching"
422    depends on CDROM_PKTCDVD
423    help
424      If enabled, write caching will be set for the CD-R/W device. For now
425      this option is dangerous unless the CD-RW media is known good, as we
426      don't do deferred write error handling yet.
427
428config ATA_OVER_ETH
429    tristate "ATA over Ethernet support"
430    depends on NET
431    help
432    This driver provides Support for ATA over Ethernet block
433    devices like the Coraid EtherDrive (R) Storage Blade.
434
435config MG_DISK
436    tristate "mGine mflash, gflash support"
437    depends on ARM && GPIOLIB
438    help
439      mGine mFlash(gFlash) block device driver
440
441config MG_DISK_RES
442    int "Size of reserved area before MBR"
443    depends on MG_DISK
444    default 0
445    help
446      Define size of reserved area that usually used for boot. Unit is KB.
447      All of the block device operation will be taken this value as start
448      offset
449      Examples:
450            1024 => 1 MB
451
452config SUNVDC
453    tristate "Sun Virtual Disk Client support"
454    depends on SUN_LDOMS
455    help
456      Support for virtual disk devices as a client under Sun
457      Logical Domains.
458
459source "drivers/s390/block/Kconfig"
460
461config XILINX_SYSACE
462    tristate "Xilinx SystemACE support"
463    depends on 4xx || MICROBLAZE
464    help
465      Include support for the Xilinx SystemACE CompactFlash interface
466
467config XEN_BLKDEV_FRONTEND
468    tristate "Xen virtual block device support"
469    depends on XEN
470    default y
471    select XEN_XENBUS_FRONTEND
472    help
473      This driver implements the front-end of the Xen virtual
474      block device driver. It communicates with a back-end driver
475      in another domain which drives the actual block device.
476
477config XEN_BLKDEV_BACKEND
478    tristate "Xen block-device backend driver"
479    depends on XEN_BACKEND
480    help
481      The block-device backend driver allows the kernel to export its
482      block devices to other guests via a high-performance shared-memory
483      interface.
484
485      The corresponding Linux frontend driver is enabled by the
486      CONFIG_XEN_BLKDEV_FRONTEND configuration option.
487
488      The backend driver attaches itself to a any block device specified
489      in the XenBus configuration. There are no limits to what the block
490      device as long as it has a major and minor.
491
492      If you are compiling a kernel to run in a Xen block backend driver
493      domain (often this is domain 0) you should say Y here. To
494      compile this driver as a module, chose M here: the module
495      will be called xen-blkback.
496
497
498config VIRTIO_BLK
499    tristate "Virtio block driver"
500    depends on VIRTIO
501    ---help---
502      This is the virtual block driver for virtio. It can be used with
503          lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
504
505config BLK_DEV_HD
506    bool "Very old hard disk (MFM/RLL/IDE) driver"
507    depends on HAVE_IDE
508    depends on !ARM || ARCH_RPC || ARCH_SHARK || BROKEN
509    help
510      This is a very old hard disk driver that lacks the enhanced
511      functionality of the newer ones.
512
513      It is required for systems with ancient MFM/RLL/ESDI drives.
514
515      If unsure, say N.
516
517config BLK_DEV_RBD
518    tristate "Rados block device (RBD)"
519    depends on INET && BLOCK
520    select CEPH_LIB
521    select LIBCRC32C
522    select CRYPTO_AES
523    select CRYPTO
524    default n
525    help
526      Say Y here if you want include the Rados block device, which stripes
527      a block device over objects stored in the Ceph distributed object
528      store.
529
530      More information at http://ceph.newdream.net/.
531
532      If unsure, say N.
533
534config BLK_DEV_RSXX
535    tristate "IBM FlashSystem 70/80 PCIe SSD Device Driver"
536    depends on PCI
537    help
538      Device driver for IBM's high speed PCIe SSD
539      storage devices: FlashSystem-70 and FlashSystem-80.
540
541      To compile this driver as a module, choose M here: the
542      module will be called rsxx.
543
544endif # BLK_DEV
545

Archive Download this file



interactive