]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.git/blame - drivers/block/Kconfig
[PATCH] pktcdvd: reusability of procfs functions
[mirror_ubuntu-bionic-kernel.git] / drivers / block / Kconfig
CommitLineData
1da177e4
LT
1#
2# Block device driver configuration
3#
4
9361401e
DH
5if BLOCK
6
1da177e4
LT
7menu "Block devices"
8
9config BLK_DEV_FD
10 tristate "Normal floppy disk support"
a08b6b79 11 depends on ARCH_MAY_HAVE_PC_FDC
1da177e4
LT
12 ---help---
13 If you want to use the floppy disk drive(s) of your PC under Linux,
14 say Y. Information about this driver, especially important for IBM
15 Thinkpad users, is contained in <file:Documentation/floppy.txt>.
16 That file also contains the location of the Floppy driver FAQ as
17 well as location of the fdutils package used to configure additional
18 parameters of the driver at run time.
19
20 To compile this driver as a module, choose M here: the
21 module will be called floppy.
22
23config AMIGA_FLOPPY
24 tristate "Amiga floppy support"
25 depends on AMIGA
26
27config ATARI_FLOPPY
28 tristate "Atari floppy support"
29 depends on ATARI
30
31config BLK_DEV_SWIM_IOP
32 bool "Macintosh IIfx/Quadra 900/Quadra 950 floppy support (EXPERIMENTAL)"
33 depends on MAC && EXPERIMENTAL && BROKEN
34 help
35 Say Y here to support the SWIM (Super Woz Integrated Machine) IOP
36 floppy controller on the Macintosh IIfx and Quadra 900/950.
37
38config MAC_FLOPPY
39 tristate "Support for PowerMac floppy"
40 depends on PPC_PMAC && !PPC_PMAC64
41 help
42 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
43 floppy controller, say Y here. Most commonly found in PowerMacs.
44
45config BLK_DEV_PS2
46 tristate "PS/2 ESDI hard disk support"
47 depends on MCA && MCA_LEGACY && BROKEN
48 help
49 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
50 hard disk.
51
52 To compile this driver as a module, choose M here: the
53 module will be called ps2esdi.
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 ATARI_ACSI
67 tristate "Atari ACSI support"
68 depends on ATARI && BROKEN
69 ---help---
70 This enables support for the Atari ACSI interface. The driver
71 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
72 be switched to that mode. Due to the ACSI command format, only disks
73 up to 1 GB are supported. Special support for certain ACSI to SCSI
74 adapters, which could relax that, isn't included yet. The ACSI
75 driver is also the basis for certain other drivers for devices
76 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
77 Ethernet, and PAMsNet Ethernet. If you want to use one of these
78 devices, you need ACSI support, too.
79
80 To compile this driver as a module, choose M here: the
81 module will be called acsi.
82
83comment "Some devices (e.g. CD jukebox) support multiple LUNs"
84 depends on ATARI && ATARI_ACSI
85
86config ACSI_MULTI_LUN
87 bool "Probe all LUNs on each ACSI device"
88 depends on ATARI_ACSI
89 help
90 If you have a ACSI device that supports more than one LUN (Logical
91 Unit Number), e.g. a CD jukebox, you should say Y here so that all
92 will be found by the ACSI driver. An ACSI device with multiple LUNs
93 acts logically like multiple ACSI devices. The vast majority of ACSI
94 devices have only one LUN, and so most people can say N here and
95 should in fact do so, because it is safer.
96
97config ATARI_SLM
98 tristate "Atari SLM laser printer support"
99 depends on ATARI && ATARI_ACSI!=n
100 help
101 If you have an Atari SLM laser printer, say Y to include support for
102 it in the kernel. Otherwise, say N. This driver is also available as
103 a module ( = code which can be inserted in and removed from the
104 running kernel whenever you want). The module will be called
105 acsi_slm. Be warned: the driver needs much ST-RAM and can cause
106 problems due to that fact!
107
108config BLK_DEV_XD
109 tristate "XT hard disk support"
a5532606 110 depends on ISA && ISA_DMA_API
1da177e4
LT
111 help
112 Very old 8 bit hard disk controllers used in the IBM XT computer
113 will be supported if you say Y here.
114
115 To compile this driver as a module, choose M here: the
116 module will be called xd.
117
118 It's pretty unlikely that you have one of these: say N.
119
120config PARIDE
121 tristate "Parallel port IDE device support"
6a19b41b 122 depends on PARPORT_PC
1da177e4
LT
123 ---help---
124 There are many external CD-ROM and disk devices that connect through
125 your computer's parallel port. Most of them are actually IDE devices
126 using a parallel port IDE adapter. This option enables the PARIDE
127 subsystem which contains drivers for many of these external drives.
128 Read <file:Documentation/paride.txt> for more information.
129
130 If you have said Y to the "Parallel-port support" configuration
131 option, you may share a single port between your printer and other
132 parallel port devices. Answer Y to build PARIDE support into your
133 kernel, or M if you would like to build it as a loadable module. If
134 your parallel port support is in a loadable module, you must build
135 PARIDE as a module. If you built PARIDE support into your kernel,
136 you may still build the individual protocol modules and high-level
137 drivers as loadable modules. If you build this support as a module,
138 it will be called paride.
139
140 To use the PARIDE support, you must say Y or M here and also to at
141 least one high-level driver (e.g. "Parallel port IDE disks",
142 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
143 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
144 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
145 etc.).
146
147source "drivers/block/paride/Kconfig"
148
149config BLK_CPQ_DA
150 tristate "Compaq SMART2 support"
151 depends on PCI
152 help
153 This is the driver for Compaq Smart Array controllers. Everyone
154 using these boards should say Y here. See the file
155 <file:Documentation/cpqarray.txt> for the current list of boards
156 supported by this driver, and for further information on the use of
157 this driver.
158
159config BLK_CPQ_CISS_DA
160 tristate "Compaq Smart Array 5xxx support"
161 depends on PCI
162 help
163 This is the driver for Compaq Smart Array 5xxx controllers.
164 Everyone using these boards should say Y here.
165 See <file:Documentation/cciss.txt> for the current list of
166 boards supported by this driver, and for further information
167 on the use of this driver.
168
169config CISS_SCSI_TAPE
170 bool "SCSI tape drive support for Smart Array 5xxx"
3e29fe83
RD
171 depends on BLK_CPQ_CISS_DA && PROC_FS
172 depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
1da177e4
LT
173 help
174 When enabled (Y), this option allows SCSI tape drives and SCSI medium
175 changers (tape robots) to be accessed via a Compaq 5xxx array
176 controller. (See <file:Documentation/cciss.txt> for more details.)
177
178 "SCSI support" and "SCSI tape support" must also be enabled for this
179 option to work.
180
181 When this option is disabled (N), the SCSI portion of the driver
182 is not compiled.
183
184config BLK_DEV_DAC960
185 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
186 depends on PCI
187 help
188 This driver adds support for the Mylex DAC960, AcceleRAID, and
189 eXtremeRAID PCI RAID controllers. See the file
190 <file:Documentation/README.DAC960> for further information about
191 this driver.
192
193 To compile this driver as a module, choose M here: the
194 module will be called DAC960.
195
196config BLK_DEV_UMEM
197 tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)"
198 depends on PCI && EXPERIMENTAL
199 ---help---
200 Saying Y here will include support for the MM5415 family of
201 battery backed (Non-volatile) RAM cards.
202 <http://www.umem.com/>
203
204 The cards appear as block devices that can be partitioned into
205 as many as 15 partitions.
206
207 To compile this driver as a module, choose M here: the
208 module will be called umem.
209
210 The umem driver has not yet been allocated a MAJOR number, so
bf6ee0ae 211 one is chosen dynamically.
1da177e4
LT
212
213config BLK_DEV_UBD
214 bool "Virtual block device"
215 depends on UML
216 ---help---
217 The User-Mode Linux port includes a driver called UBD which will let
218 you access arbitrary files on the host computer as block devices.
219 Unless you know that you do not need such virtual block devices say
220 Y here.
221
222config BLK_DEV_UBD_SYNC
223 bool "Always do synchronous disk IO for UBD"
224 depends on BLK_DEV_UBD
225 ---help---
226 Writes to the virtual block device are not immediately written to the
227 host's disk; this may cause problems if, for example, the User-Mode
228 Linux 'Virtual Machine' uses a journalling filesystem and the host
229 computer crashes.
230
231 Synchronous operation (i.e. always writing data to the host's disk
232 immediately) is configurable on a per-UBD basis by using a special
233 kernel command line option. Alternatively, you can say Y here to
234 turn on synchronous operation by default for all block devices.
235
236 If you're running a journalling file system (like reiserfs, for
237 example) in your virtual machine, you will want to say Y here. If
238 you care for the safety of the data in your virtual machine, Y is a
239 wise choice too. In all other cases (for example, if you're just
240 playing around with User-Mode Linux) you can choose N.
241
242config BLK_DEV_COW_COMMON
243 bool
244 default BLK_DEV_UBD
245
246config MMAPPER
247 tristate "Example IO memory driver (BROKEN)"
248 depends on UML && BROKEN
249 ---help---
250 The User-Mode Linux port can provide support for IO Memory
251 emulation with this option. This allows a host file to be
252 specified as an I/O region on the kernel command line. That file
253 will be mapped into UML's kernel address space where a driver can
254 locate it and do whatever it wants with the memory, including
255 providing an interface to it for UML processes to use.
256
257 For more information, see
258 <http://user-mode-linux.sourceforge.net/iomem.html>.
259
260 If you'd like to be able to provide a simulated IO port space for
261 User-Mode Linux processes, say Y. If unsure, say N.
262
263config BLK_DEV_LOOP
264 tristate "Loopback device support"
265 ---help---
266 Saying Y here will allow you to use a regular file as a block
267 device; you can then create a file system on that block device and
268 mount it just as you would mount other block devices such as hard
269 drive partitions, CD-ROM drives or floppy drives. The loop devices
270 are block special device files with major number 7 and typically
271 called /dev/loop0, /dev/loop1 etc.
272
273 This is useful if you want to check an ISO 9660 file system before
274 burning the CD, or if you want to use floppy images without first
275 writing them to floppy. Furthermore, some Linux distributions avoid
276 the need for a dedicated Linux partition by keeping their complete
277 root file system inside a DOS FAT file using this loop device
278 driver.
279
280 To use the loop device, you need the losetup utility, found in the
281 util-linux package, see
282 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
283
284 The loop device driver can also be used to "hide" a file system in
285 a disk partition, floppy, or regular file, either using encryption
286 (scrambling the data) or steganography (hiding the data in the low
287 bits of, say, a sound file). This is also safe if the file resides
288 on a remote file server.
289
290 There are several ways of encrypting disks. Some of these require
291 kernel patches. The vanilla kernel offers the cryptoloop option
292 and a Device Mapper target (which is superior, as it supports all
293 file systems). If you want to use the cryptoloop, say Y to both
294 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
295 or later) version of util-linux. Additionally, be aware that
296 the cryptoloop is not safe for storing journaled filesystems.
297
298 Note that this loop device has nothing to do with the loopback
299 device used for network connections from the machine to itself.
300
301 To compile this driver as a module, choose M here: the
302 module will be called loop.
303
304 Most users will answer N here.
305
306config BLK_DEV_CRYPTOLOOP
307 tristate "Cryptoloop Support"
308 select CRYPTO
8df3b0a2 309 select CRYPTO_CBC
1da177e4
LT
310 depends on BLK_DEV_LOOP
311 ---help---
312 Say Y here if you want to be able to use the ciphers that are
313 provided by the CryptoAPI as loop transformation. This might be
314 used as hard disk encryption.
315
316 WARNING: This device is not safe for journaled file systems like
317 ext3 or Reiserfs. Please use the Device Mapper crypto module
318 instead, which can be configured to be on-disk compatible with the
319 cryptoloop device.
320
321config BLK_DEV_NBD
322 tristate "Network block device support"
323 depends on NET
324 ---help---
325 Saying Y here will allow your computer to be a client for network
326 block devices, i.e. it will be able to use block devices exported by
327 servers (mount file systems on them etc.). Communication between
328 client and server works over TCP/IP networking, but to the client
329 program this is hidden: it looks like a regular local file access to
330 a block device special file such as /dev/nd0.
331
332 Network block devices also allows you to run a block-device in
333 userland (making server and client physically the same computer,
334 communicating using the loopback network device).
335
336 Read <file:Documentation/nbd.txt> for more information, especially
337 about where to find the server code, which runs in user space and
338 does not need special kernel support.
339
340 Note that this has nothing to do with the network file systems NFS
341 or Coda; you can say N here even if you intend to use NFS or Coda.
342
343 To compile this driver as a module, choose M here: the
344 module will be called nbd.
345
346 If unsure, say N.
347
348config BLK_DEV_SX8
349 tristate "Promise SATA SX8 support"
350 depends on PCI
351 ---help---
352 Saying Y or M here will enable support for the
353 Promise SATA SX8 controllers.
354
355 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
356
357config BLK_DEV_UB
358 tristate "Low Performance USB Block driver"
359 depends on USB
360 help
361 This driver supports certain USB attached storage devices
362 such as flash keys.
363
a00828e9
PZ
364 If you enable this driver, it is recommended to avoid conflicts
365 with usb-storage by enabling USB_LIBUSUAL.
1da177e4
LT
366
367 If unsure, say N.
368
369config BLK_DEV_RAM
370 tristate "RAM disk support"
371 ---help---
372 Saying Y here will allow you to use a portion of your RAM memory as
373 a block device, so that you can make file systems on it, read and
374 write to it and do all the other things that you can do with normal
375 block devices (such as hard drives). It is usually used to load and
376 store a copy of a minimal root file system off of a floppy into RAM
377 during the initial install of Linux.
378
379 Note that the kernel command line option "ramdisk=XX" is now
380 obsolete. For details, read <file:Documentation/ramdisk.txt>.
381
382 To compile this driver as a module, choose M here: the
383 module will be called rd.
384
385 Most normal users won't need the RAM disk functionality, and can
386 thus say N here.
387
388config BLK_DEV_RAM_COUNT
a687fb18 389 int "Default number of RAM disks"
1da177e4 390 default "16"
a687fb18 391 depends on BLK_DEV_RAM
1da177e4
LT
392 help
393 The default value is 16 RAM disks. Change this if you know what
394 are doing. If you boot from a filesystem that needs to be extracted
395 in memory, you will need at least one RAM disk (e.g. root on cramfs).
396
397config BLK_DEV_RAM_SIZE
398 int "Default RAM disk size (kbytes)"
399 depends on BLK_DEV_RAM
400 default "4096"
401 help
402 The default value is 4096 kilobytes. Only change this if you know
403 what are you doing. If you are using IBM S/390, then set this to
404 8192.
405
bef317e3
NS
406config BLK_DEV_RAM_BLOCKSIZE
407 int "Default RAM disk block size (bytes)"
408 depends on BLK_DEV_RAM
409 default "1024"
410 help
73cf9630 411 The default value is 1024 bytes. PAGE_SIZE is a much more
bef317e3
NS
412 efficient choice however. The default is kept to ensure initrd
413 setups function - apparently needed by the rd_load_image routine
414 that supposes the filesystem in the image uses a 1024 blocksize.
415
1da177e4 416config BLK_DEV_INITRD
1751ace0 417 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
ffca1110 418 depends on BROKEN || !FRV
1da177e4 419 help
1751ace0
PA
420 The initial RAM filesystem is a ramfs which is loaded by the
421 boot loader (loadlin or lilo) and that is mounted as root
422 before the normal boot procedure. It is typically used to
423 load modules needed to mount the "real" root file system,
424 etc. See <file:Documentation/initrd.txt> for details.
425
426 If RAM disk support (BLK_DEV_RAM) is also included, this
427 also enables initial RAM disk (initrd) support.
1da177e4 428
1da177e4 429
1da177e4
LT
430config CDROM_PKTCDVD
431 tristate "Packet writing on CD/DVD media"
432 depends on !UML
433 help
434 If you have a CDROM drive that supports packet writing, say Y to
435 include preliminary support. It should work with any MMC/Mt Fuji
436 compliant ATAPI or SCSI drive, which is just about any newer CD
437 writer.
438
439 Currently only writing to CD-RW, DVD-RW and DVD+RW discs is possible.
440 DVD-RW disks must be in restricted overwrite mode.
441
442 To compile this driver as a module, choose M here: the
443 module will be called pktcdvd.
444
445config CDROM_PKTCDVD_BUFFERS
446 int "Free buffers for data gathering"
447 depends on CDROM_PKTCDVD
448 default "8"
449 help
450 This controls the maximum number of active concurrent packets. More
451 concurrent packets can increase write performance, but also require
452 more memory. Each concurrent packet will require approximately 64Kb
e1bc89bc
PO
453 of non-swappable kernel memory, memory which will be allocated when
454 a disc is opened for writing.
1da177e4
LT
455
456config CDROM_PKTCDVD_WCACHE
b566ccef
AB
457 bool "Enable write caching (EXPERIMENTAL)"
458 depends on CDROM_PKTCDVD && EXPERIMENTAL
1da177e4
LT
459 help
460 If enabled, write caching will be set for the CD-R/W device. For now
461 this option is dangerous unless the CD-RW media is known good, as we
462 don't do deferred write error handling yet.
463
464source "drivers/s390/block/Kconfig"
465
1da177e4
LT
466config ATA_OVER_ETH
467 tristate "ATA over Ethernet support"
468 depends on NET
469 help
470 This driver provides Support for ATA over Ethernet block
471 devices like the Coraid EtherDrive (R) Storage Blade.
472
473endmenu
9361401e
DH
474
475endif