write in 30M

hc

2024-02-20 ea08eeccae9297f7aabd2ef7f0c2517ac4549acc

 kernel/drivers/block/Kconfig
..
..
@@ -7,7 +7,7 @@
7
7
 	bool "Block devices"
8
8
 	depends on BLOCK
9
9
 	default y
10
-	---help---
10
+	help
11
11
 	  Say Y here to get to see options for various different block device
12
12
 	  drivers. This option alone does not add any kernel code.
13
13
 
..
..
@@ -16,28 +16,38 @@
16
16
 
17
17
 if BLK_DEV
18
18
 
19
-config BLK_DEV_NULL_BLK
20
-	tristate "Null test block driver"
21
-	select CONFIGFS_FS
22
-
23
-config BLK_DEV_NULL_BLK_FAULT_INJECTION
24
-	bool "Support fault injection for Null test block driver"
25
-	depends on BLK_DEV_NULL_BLK && FAULT_INJECTION
19
+source "drivers/block/null_blk/Kconfig"
26
20
 
27
21
 config BLK_DEV_FD
28
22
 	tristate "Normal floppy disk support"
29
23
 	depends on ARCH_MAY_HAVE_PC_FDC
30
-	---help---
24
+	help
31
25
 	  If you want to use the floppy disk drive(s) of your PC under Linux,
32
26
 	  say Y. Information about this driver, especially important for IBM
33
27
 	  Thinkpad users, is contained in
34
-	  <file:Documentation/blockdev/floppy.txt>.
28
+	  <file:Documentation/admin-guide/blockdev/floppy.rst>.
35
29
 	  That file also contains the location of the Floppy driver FAQ as
36
30
 	  well as location of the fdutils package used to configure additional
37
31
 	  parameters of the driver at run time.
38
32
 
39
33
 	  To compile this driver as a module, choose M here: the
40
34
 	  module will be called floppy.
35
+
36
+config BLK_DEV_FD_RAWCMD
37
+	bool "Support for raw floppy disk commands (DEPRECATED)"
38
+	depends on BLK_DEV_FD
39
+	help
40
+	  If you want to use actual physical floppies and expect to do
41
+	  special low-level hardware accesses to them (access and use
42
+	  non-standard formats, for example), then enable this.
43
+
44
+	  Note that the code enabled by this option is rarely used and
45
+	  might be unstable or insecure, and distros should not enable it.
46
+
47
+	  Note: FDRAWCMD is deprecated and will be removed from the kernel
48
+	  in the near future.
49
+
50
+	  If unsure, say N.
41
51
 
42
52
 config AMIGA_FLOPPY
43
53
 	tristate "Amiga floppy support"
..
..
@@ -91,12 +101,12 @@
91
101
 config PARIDE
92
102
 	tristate "Parallel port IDE device support"
93
103
 	depends on PARPORT_PC
94
-	---help---
104
+	help
95
105
 	  There are many external CD-ROM and disk devices that connect through
96
106
 	  your computer's parallel port. Most of them are actually IDE devices
97
107
 	  using a parallel port IDE adapter. This option enables the PARIDE
98
108
 	  subsystem which contains drivers for many of these external drives.
99
-	  Read <file:Documentation/blockdev/paride.txt> for more information.
109
+	  Read <file:Documentation/admin-guide/blockdev/paride.rst> for more information.
100
110
 
101
111
 	  If you have said Y to the "Parallel-port support" configuration
102
112
 	  option, you may share a single port between your printer and other
..
..
@@ -121,22 +131,10 @@
121
131
 
122
132
 source "drivers/block/zram/Kconfig"
123
133
 
124
-config BLK_DEV_DAC960
125
-	tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
126
-	depends on PCI
127
-	help
128
-	  This driver adds support for the Mylex DAC960, AcceleRAID, and
129
-	  eXtremeRAID PCI RAID controllers.  See the file
130
-	  <file:Documentation/blockdev/README.DAC960> for further information
131
-	  about this driver.
132
-
133
-	  To compile this driver as a module, choose M here: the
134
-	  module will be called DAC960.
135
-
136
134
 config BLK_DEV_UMEM
137
135
 	tristate "Micro Memory MM5415 Battery Backed RAM support"
138
136
 	depends on PCI
139
-	---help---
137
+	help
140
138
 	  Saying Y here will include support for the MM5415 family of
141
139
 	  battery backed (Non-volatile) RAM cards.
142
140
 	  <http://www.umem.com/>
..
..
@@ -153,7 +151,7 @@
153
151
 config BLK_DEV_UBD
154
152
 	bool "Virtual block device"
155
153
 	depends on UML
156
-	---help---
154
+	help
157
155
           The User-Mode Linux port includes a driver called UBD which will let
158
156
           you access arbitrary files on the host computer as block devices.
159
157
           Unless you know that you do not need such virtual block devices say
..
..
@@ -162,7 +160,7 @@
162
160
 config BLK_DEV_UBD_SYNC
163
161
 	bool "Always do synchronous disk IO for UBD"
164
162
 	depends on BLK_DEV_UBD
165
-	---help---
163
+	help
166
164
 	  Writes to the virtual block device are not immediately written to the
167
165
 	  host's disk; this may cause problems if, for example, the User-Mode
168
166
 	  Linux 'Virtual Machine' uses a journalling filesystem and the host
..
..
@@ -185,7 +183,7 @@
185
183
 
186
184
 config BLK_DEV_LOOP
187
185
 	tristate "Loopback device support"
188
-	---help---
186
+	help
189
187
 	  Saying Y here will allow you to use a regular file as a block
190
188
 	  device; you can then create a file system on that block device and
191
189
 	  mount it just as you would mount other block devices such as hard
..
..
@@ -246,7 +244,7 @@
246
244
 	select CRYPTO
247
245
 	select CRYPTO_CBC
248
246
 	depends on BLK_DEV_LOOP
249
-	---help---
247
+	help
250
248
 	  Say Y here if you want to be able to use the ciphers that are 
251
249
 	  provided by the CryptoAPI as loop transformation. This might be
252
250
 	  used as hard disk encryption.
..
..
@@ -261,7 +259,7 @@
261
259
 config BLK_DEV_NBD
262
260
 	tristate "Network block device support"
263
261
 	depends on NET
264
-	---help---
262
+	help
265
263
 	  Saying Y here will allow your computer to be a client for network
266
264
 	  block devices, i.e. it will be able to use block devices exported by
267
265
 	  servers (mount file systems on them etc.). Communication between
..
..
@@ -273,7 +271,7 @@
273
271
 	  userland (making server and client physically the same computer,
274
272
 	  communicating using the loopback network device).
275
273
 
276
-	  Read <file:Documentation/blockdev/nbd.txt> for more information,
274
+	  Read <file:Documentation/admin-guide/blockdev/nbd.rst> for more information,
277
275
 	  especially about where to find the server code, which runs in user
278
276
 	  space and does not need special kernel support.
279
277
 
..
..
@@ -289,24 +287,15 @@
289
287
 	tristate "STEC S1120 Block Driver"
290
288
 	depends on PCI
291
289
 	depends on 64BIT
292
-	---help---
290
+	help
293
291
 	Saying Y or M here will enable support for the
294
292
 	STEC, Inc. S1120 PCIe SSD.
295
293
 
296
294
 	Use device /dev/skd$N amd /dev/skd$Np$M.
297
295
 
298
-config BLK_DEV_SX8
299
-	tristate "Promise SATA SX8 support"
300
-	depends on PCI
301
-	---help---
302
-	  Saying Y or M here will enable support for the 
303
-	  Promise SATA SX8 controllers.
304
-
305
-	  Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
306
-
307
296
 config BLK_DEV_RAM
308
297
 	tristate "RAM block device support"
309
-	---help---
298
+	help
310
299
 	  Saying Y here will allow you to use a portion of your RAM memory as
311
300
 	  a block device, so that you can make file systems on it, read and
312
301
 	  write to it and do all the other things that you can do with normal
..
..
@@ -315,7 +304,7 @@
315
304
 	  during the initial install of Linux.
316
305
 
317
306
 	  Note that the kernel command line option "ramdisk=XX" is now obsolete.
318
-	  For details, read <file:Documentation/blockdev/ramdisk.txt>.
307
+	  For details, read <file:Documentation/admin-guide/blockdev/ramdisk.rst>.
319
308
 
320
309
 	  To compile this driver as a module, choose M here: the
321
310
 	  module will be called brd. An alias "rd" has been defined
..
..
@@ -359,7 +348,7 @@
359
348
 	  is possible.
360
349
 	  DVD-RW disks must be in restricted overwrite mode.
361
350
 
362
-	  See the file <file:Documentation/cdrom/packet-writing.txt>
351
+	  See the file <file:Documentation/cdrom/packet-writing.rst>
363
352
 	  for further information on the use of this driver.
364
353
 
365
354
 	  To compile this driver as a module, choose M here: the
..
..
@@ -440,19 +429,9 @@
440
429
 config VIRTIO_BLK
441
430
 	tristate "Virtio block driver"
442
431
 	depends on VIRTIO
443
-	---help---
432
+	help
444
433
 	  This is the virtual block driver for virtio.  It can be used with
445
434
           QEMU based VMMs (like KVM or Xen).  Say Y or M.
446
-
447
-config VIRTIO_BLK_SCSI
448
-	bool "SCSI passthrough request for the Virtio block driver"
449
-	depends on VIRTIO_BLK
450
-	select BLK_SCSI_REQUEST
451
-	---help---
452
-	  Enable support for SCSI passthrough (e.g. the SG_IO ioctl) on
453
-	  virtio-blk devices.  This is only supported for the legacy
454
-	  virtio protocol and not enabled by default by any hypervisor.
455
-	  You probably want to use virtio-scsi instead.
456
435
 
457
436
 config BLK_DEV_RBD
458
437
 	tristate "Rados block device (RBD)"
..
..
@@ -461,7 +440,6 @@
461
440
 	select LIBCRC32C
462
441
 	select CRYPTO_AES
463
442
 	select CRYPTO
464
-	default n
465
443
 	help
466
444
 	  Say Y here if you want include the Rados block device, which stripes
467
445
 	  a block device over objects stored in the Ceph distributed object
..
..
@@ -482,4 +460,6 @@
482
460
 	  To compile this driver as a module, choose M here: the
483
461
 	  module will be called rsxx.
484
462
 
463
+source "drivers/block/rnbd/Kconfig"
464
+
485
465
 endif # BLK_DEV