]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Block device driver configuration | |
3 | # | |
4 | ||
fd11d171 JE |
5 | menuconfig BLK_DEV |
6 | bool "Block devices" | |
7 | depends on BLOCK | |
8 | default y | |
06bfb7eb JE |
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. | |
9361401e | 15 | |
fd11d171 | 16 | if BLK_DEV |
1da177e4 LT |
17 | |
18 | config BLK_DEV_FD | |
19 | tristate "Normal floppy disk support" | |
a08b6b79 | 20 | depends on ARCH_MAY_HAVE_PC_FDC |
1da177e4 LT |
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 <file:Documentation/floppy.txt>. | |
25 | That file also contains the location of the Floppy driver FAQ as | |
26 | well as location of the fdutils package used to configure additional | |
27 | parameters of the driver at run time. | |
28 | ||
29 | To compile this driver as a module, choose M here: the | |
30 | module will be called floppy. | |
31 | ||
32 | config AMIGA_FLOPPY | |
33 | tristate "Amiga floppy support" | |
34 | depends on AMIGA | |
35 | ||
36 | config ATARI_FLOPPY | |
37 | tristate "Atari floppy support" | |
38 | depends on ATARI | |
39 | ||
1da177e4 LT |
40 | config MAC_FLOPPY |
41 | tristate "Support for PowerMac floppy" | |
42 | depends on PPC_PMAC && !PPC_PMAC64 | |
43 | help | |
44 | If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple) | |
45 | floppy controller, say Y here. Most commonly found in PowerMacs. | |
46 | ||
47 | config BLK_DEV_PS2 | |
48 | tristate "PS/2 ESDI hard disk support" | |
49 | depends on MCA && MCA_LEGACY && BROKEN | |
50 | help | |
51 | Say Y here if you have a PS/2 machine with a MCA bus and an ESDI | |
52 | hard disk. | |
53 | ||
54 | To compile this driver as a module, choose M here: the | |
55 | module will be called ps2esdi. | |
56 | ||
57 | config AMIGA_Z2RAM | |
58 | tristate "Amiga Zorro II ramdisk support" | |
59 | depends on ZORRO | |
60 | help | |
61 | This enables support for using Chip RAM and Zorro II RAM as a | |
62 | ramdisk or as a swap partition. Say Y if you want to include this | |
63 | driver in the kernel. | |
64 | ||
65 | To compile this driver as a module, choose M here: the | |
66 | module will be called z2ram. | |
67 | ||
1da177e4 LT |
68 | config BLK_DEV_XD |
69 | tristate "XT hard disk support" | |
a5532606 | 70 | depends on ISA && ISA_DMA_API |
1da177e4 LT |
71 | help |
72 | Very old 8 bit hard disk controllers used in the IBM XT computer | |
73 | will be supported if you say Y here. | |
74 | ||
75 | To compile this driver as a module, choose M here: the | |
76 | module will be called xd. | |
77 | ||
78 | It's pretty unlikely that you have one of these: say N. | |
79 | ||
80 | config PARIDE | |
81 | tristate "Parallel port IDE device support" | |
6a19b41b | 82 | depends on PARPORT_PC |
1da177e4 LT |
83 | ---help--- |
84 | There are many external CD-ROM and disk devices that connect through | |
85 | your computer's parallel port. Most of them are actually IDE devices | |
86 | using a parallel port IDE adapter. This option enables the PARIDE | |
87 | subsystem which contains drivers for many of these external drives. | |
88 | Read <file:Documentation/paride.txt> for more information. | |
89 | ||
90 | If you have said Y to the "Parallel-port support" configuration | |
91 | option, you may share a single port between your printer and other | |
92 | parallel port devices. Answer Y to build PARIDE support into your | |
93 | kernel, or M if you would like to build it as a loadable module. If | |
94 | your parallel port support is in a loadable module, you must build | |
95 | PARIDE as a module. If you built PARIDE support into your kernel, | |
96 | you may still build the individual protocol modules and high-level | |
97 | drivers as loadable modules. If you build this support as a module, | |
98 | it will be called paride. | |
99 | ||
100 | To use the PARIDE support, you must say Y or M here and also to at | |
101 | least one high-level driver (e.g. "Parallel port IDE disks", | |
102 | "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and | |
103 | to at least one protocol driver (e.g. "ATEN EH-100 protocol", | |
104 | "MicroSolutions backpack protocol", "DataStor Commuter protocol" | |
105 | etc.). | |
106 | ||
107 | source "drivers/block/paride/Kconfig" | |
108 | ||
109 | config BLK_CPQ_DA | |
110 | tristate "Compaq SMART2 support" | |
f057eac0 | 111 | depends on PCI && VIRT_TO_BUS |
1da177e4 LT |
112 | help |
113 | This is the driver for Compaq Smart Array controllers. Everyone | |
114 | using these boards should say Y here. See the file | |
115 | <file:Documentation/cpqarray.txt> for the current list of boards | |
116 | supported by this driver, and for further information on the use of | |
117 | this driver. | |
118 | ||
119 | config BLK_CPQ_CISS_DA | |
120 | tristate "Compaq Smart Array 5xxx support" | |
121 | depends on PCI | |
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/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 | ||
129 | config CISS_SCSI_TAPE | |
130 | bool "SCSI tape drive support for Smart Array 5xxx" | |
3e29fe83 RD |
131 | depends on BLK_CPQ_CISS_DA && PROC_FS |
132 | depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA | |
1da177e4 LT |
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/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 | ||
144 | config 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/README.DAC960> for further information about | |
151 | this driver. | |
152 | ||
153 | To compile this driver as a module, choose M here: the | |
154 | module will be called DAC960. | |
155 | ||
156 | config BLK_DEV_UMEM | |
157 | tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)" | |
158 | depends on PCI && EXPERIMENTAL | |
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 | |
bf6ee0ae | 171 | one is chosen dynamically. |
1da177e4 LT |
172 | |
173 | config 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 | ||
182 | config 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 | ||
202 | config BLK_DEV_COW_COMMON | |
203 | bool | |
204 | default BLK_DEV_UBD | |
205 | ||
206 | config MMAPPER | |
207 | tristate "Example IO memory driver (BROKEN)" | |
208 | depends on UML && BROKEN | |
209 | ---help--- | |
210 | The User-Mode Linux port can provide support for IO Memory | |
211 | emulation with this option. This allows a host file to be | |
212 | specified as an I/O region on the kernel command line. That file | |
213 | will be mapped into UML's kernel address space where a driver can | |
214 | locate it and do whatever it wants with the memory, including | |
215 | providing an interface to it for UML processes to use. | |
216 | ||
217 | For more information, see | |
218 | <http://user-mode-linux.sourceforge.net/iomem.html>. | |
219 | ||
220 | If you'd like to be able to provide a simulated IO port space for | |
221 | User-Mode Linux processes, say Y. If unsure, say N. | |
222 | ||
223 | config BLK_DEV_LOOP | |
224 | tristate "Loopback device support" | |
225 | ---help--- | |
226 | Saying Y here will allow you to use a regular file as a block | |
227 | device; you can then create a file system on that block device and | |
228 | mount it just as you would mount other block devices such as hard | |
229 | drive partitions, CD-ROM drives or floppy drives. The loop devices | |
230 | are block special device files with major number 7 and typically | |
231 | called /dev/loop0, /dev/loop1 etc. | |
232 | ||
233 | This is useful if you want to check an ISO 9660 file system before | |
234 | burning the CD, or if you want to use floppy images without first | |
235 | writing them to floppy. Furthermore, some Linux distributions avoid | |
236 | the need for a dedicated Linux partition by keeping their complete | |
237 | root file system inside a DOS FAT file using this loop device | |
238 | driver. | |
239 | ||
240 | To use the loop device, you need the losetup utility, found in the | |
241 | util-linux package, see | |
242 | <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>. | |
243 | ||
244 | The loop device driver can also be used to "hide" a file system in | |
245 | a disk partition, floppy, or regular file, either using encryption | |
246 | (scrambling the data) or steganography (hiding the data in the low | |
247 | bits of, say, a sound file). This is also safe if the file resides | |
248 | on a remote file server. | |
249 | ||
250 | There are several ways of encrypting disks. Some of these require | |
251 | kernel patches. The vanilla kernel offers the cryptoloop option | |
252 | and a Device Mapper target (which is superior, as it supports all | |
253 | file systems). If you want to use the cryptoloop, say Y to both | |
254 | LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12 | |
255 | or later) version of util-linux. Additionally, be aware that | |
256 | the cryptoloop is not safe for storing journaled filesystems. | |
257 | ||
258 | Note that this loop device has nothing to do with the loopback | |
259 | device used for network connections from the machine to itself. | |
260 | ||
261 | To compile this driver as a module, choose M here: the | |
262 | module will be called loop. | |
263 | ||
264 | Most users will answer N here. | |
265 | ||
266 | config BLK_DEV_CRYPTOLOOP | |
267 | tristate "Cryptoloop Support" | |
268 | select CRYPTO | |
8df3b0a2 | 269 | select CRYPTO_CBC |
1da177e4 LT |
270 | depends on BLK_DEV_LOOP |
271 | ---help--- | |
272 | Say Y here if you want to be able to use the ciphers that are | |
273 | provided by the CryptoAPI as loop transformation. This might be | |
274 | used as hard disk encryption. | |
275 | ||
276 | WARNING: This device is not safe for journaled file systems like | |
277 | ext3 or Reiserfs. Please use the Device Mapper crypto module | |
278 | instead, which can be configured to be on-disk compatible with the | |
279 | cryptoloop device. | |
280 | ||
281 | config 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/nbd.txt> for more information, especially | |
297 | about where to find the server code, which runs in user space and | |
298 | 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 | ||
308 | config BLK_DEV_SX8 | |
309 | tristate "Promise SATA SX8 support" | |
310 | depends on PCI | |
311 | ---help--- | |
312 | Saying Y or M here will enable support for the | |
313 | Promise SATA SX8 controllers. | |
314 | ||
315 | Use devices /dev/sx8/$N and /dev/sx8/$Np$M. | |
316 | ||
317 | config BLK_DEV_UB | |
318 | tristate "Low Performance USB Block driver" | |
319 | depends on USB | |
320 | help | |
321 | This driver supports certain USB attached storage devices | |
322 | such as flash keys. | |
323 | ||
a00828e9 PZ |
324 | If you enable this driver, it is recommended to avoid conflicts |
325 | with usb-storage by enabling USB_LIBUSUAL. | |
1da177e4 LT |
326 | |
327 | If unsure, say N. | |
328 | ||
329 | config BLK_DEV_RAM | |
330 | tristate "RAM disk support" | |
331 | ---help--- | |
332 | Saying Y here will allow you to use a portion of your RAM memory as | |
333 | a block device, so that you can make file systems on it, read and | |
334 | write to it and do all the other things that you can do with normal | |
335 | block devices (such as hard drives). It is usually used to load and | |
336 | store a copy of a minimal root file system off of a floppy into RAM | |
337 | during the initial install of Linux. | |
338 | ||
339 | Note that the kernel command line option "ramdisk=XX" is now | |
340 | obsolete. For details, read <file:Documentation/ramdisk.txt>. | |
341 | ||
342 | To compile this driver as a module, choose M here: the | |
343 | module will be called rd. | |
344 | ||
345 | Most normal users won't need the RAM disk functionality, and can | |
346 | thus say N here. | |
347 | ||
348 | config BLK_DEV_RAM_COUNT | |
a687fb18 | 349 | int "Default number of RAM disks" |
1da177e4 | 350 | default "16" |
a687fb18 | 351 | depends on BLK_DEV_RAM |
1da177e4 LT |
352 | help |
353 | The default value is 16 RAM disks. Change this if you know what | |
354 | are doing. If you boot from a filesystem that needs to be extracted | |
355 | in memory, you will need at least one RAM disk (e.g. root on cramfs). | |
356 | ||
357 | config BLK_DEV_RAM_SIZE | |
358 | int "Default RAM disk size (kbytes)" | |
359 | depends on BLK_DEV_RAM | |
360 | default "4096" | |
361 | help | |
362 | The default value is 4096 kilobytes. Only change this if you know | |
363 | what are you doing. If you are using IBM S/390, then set this to | |
364 | 8192. | |
365 | ||
bef317e3 NS |
366 | config BLK_DEV_RAM_BLOCKSIZE |
367 | int "Default RAM disk block size (bytes)" | |
368 | depends on BLK_DEV_RAM | |
369 | default "1024" | |
370 | help | |
73cf9630 | 371 | The default value is 1024 bytes. PAGE_SIZE is a much more |
bef317e3 NS |
372 | efficient choice however. The default is kept to ensure initrd |
373 | setups function - apparently needed by the rd_load_image routine | |
374 | that supposes the filesystem in the image uses a 1024 blocksize. | |
375 | ||
1da177e4 LT |
376 | config CDROM_PKTCDVD |
377 | tristate "Packet writing on CD/DVD media" | |
378 | depends on !UML | |
379 | help | |
2d4eeec5 TM |
380 | If you have a CDROM/DVD drive that supports packet writing, say |
381 | Y to include support. It should work with any MMC/Mt Fuji | |
382 | compliant ATAPI or SCSI drive, which is just about any newer | |
383 | DVD/CD writer. | |
1da177e4 | 384 | |
2d4eeec5 TM |
385 | Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs |
386 | is possible. | |
1da177e4 LT |
387 | DVD-RW disks must be in restricted overwrite mode. |
388 | ||
2d4eeec5 TM |
389 | See the file <file:Documentation/cdrom/packet-writing.txt> |
390 | for further information on the use of this driver. | |
391 | ||
1da177e4 LT |
392 | To compile this driver as a module, choose M here: the |
393 | module will be called pktcdvd. | |
394 | ||
395 | config CDROM_PKTCDVD_BUFFERS | |
396 | int "Free buffers for data gathering" | |
397 | depends on CDROM_PKTCDVD | |
398 | default "8" | |
399 | help | |
400 | This controls the maximum number of active concurrent packets. More | |
401 | concurrent packets can increase write performance, but also require | |
402 | more memory. Each concurrent packet will require approximately 64Kb | |
e1bc89bc PO |
403 | of non-swappable kernel memory, memory which will be allocated when |
404 | a disc is opened for writing. | |
1da177e4 LT |
405 | |
406 | config CDROM_PKTCDVD_WCACHE | |
b566ccef AB |
407 | bool "Enable write caching (EXPERIMENTAL)" |
408 | depends on CDROM_PKTCDVD && EXPERIMENTAL | |
1da177e4 LT |
409 | help |
410 | If enabled, write caching will be set for the CD-R/W device. For now | |
411 | this option is dangerous unless the CD-RW media is known good, as we | |
412 | don't do deferred write error handling yet. | |
413 | ||
1da177e4 LT |
414 | config ATA_OVER_ETH |
415 | tristate "ATA over Ethernet support" | |
416 | depends on NET | |
417 | help | |
418 | This driver provides Support for ATA over Ethernet block | |
419 | devices like the Coraid EtherDrive (R) Storage Blade. | |
420 | ||
667ef3c3 DM |
421 | config SUNVDC |
422 | tristate "Sun Virtual Disk Client support" | |
423 | depends on SUN_LDOMS | |
424 | help | |
425 | Support for virtual disk devices as a client under Sun | |
426 | Logical Domains. | |
427 | ||
61d48c2c MS |
428 | source "drivers/s390/block/Kconfig" |
429 | ||
74489a91 GL |
430 | config XILINX_SYSACE |
431 | tristate "Xilinx SystemACE support" | |
432 | depends on 4xx | |
433 | help | |
434 | Include support for the Xilinx SystemACE CompactFlash interface | |
435 | ||
9f27ee59 JF |
436 | config XEN_BLKDEV_FRONTEND |
437 | tristate "Xen virtual block device support" | |
438 | depends on XEN | |
439 | default y | |
440 | help | |
441 | This driver implements the front-end of the Xen virtual | |
442 | block device driver. It communicates with a back-end driver | |
443 | in another domain which drives the actual block device. | |
444 | ||
fd11d171 | 445 | endif # BLK_DEV |