1 files changed, 0 insertions, 330 deletions
diff --git a/drivers/char/ftape/Kconfig b/drivers/char/ftape/Kconfig
deleted file mode 100644
index 0d65189a7ae8..000000000000
--- a/drivers/char/ftape/Kconfig
+++ /dev/null
@@ -1,330 +0,0 @@
-#
-# Ftape configuration
-#
-config ZFTAPE
-        tristate "Zftape, the VFS interface"
-        depends on FTAPE
-        ---help---
-          Normally, you want to say Y or M. DON'T say N here or you
-          WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
-          The ftape module itself no longer contains the routines necessary
-          to interface with the kernel VFS layer (i.e. to actually write data
-          to and read data from the tape drive).  Instead the file system
-          interface (i.e. the hardware independent part of the driver) has
-          been moved to a separate module.
-          To compile this driver as a module, choose M here: the
-          module will be called zftape.
-          Regardless of whether you say Y or M here, an additional runtime
-          loadable module called `zft-compressor' which contains code to
-          support user transparent on-the-fly compression based on Ross
-          William's lzrw3 algorithm will be produced.  If you have enabled the
-          kernel module loader (i.e. have said Y to "Kernel module loader
-          support", above) then `zft-compressor' will be loaded
-          automatically by zftape when needed.
-          Despite its name, zftape does NOT use compression by default.
-config ZFT_DFLT_BLK_SZ
-        int "Default block size"
-        depends on ZFTAPE
-        default "10240"
-        ---help---
-          If unsure leave this at its default value, i.e. 10240. Note that
-          you specify only the default block size here. The block size can be
-          changed at run time using the MTSETBLK tape operation with the
-          MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
-          shell command line).
-          The probably most striking difference between zftape and previous
-          versions of ftape is the fact that all data must be written or read
-          in multiples of a fixed block size. The block size defaults to
-          10240 which is what GNU tar uses. The values for the block size
-          should be either 1 or multiples of 1024 up to a maximum value of
-          63488 (i.e. 62 K). If you specify `1' then zftape's builtin
-          compression will be disabled.
-          Reasonable values are `10240' (GNU tar's default block size),
-          `5120' (afio's default block size), `32768' (default block size some
-          backup programs assume for SCSI tape drives) or `1' (no restriction
-          on block size, but disables builtin compression).
-comment "The compressor will be built as a module only!"
-        depends on FTAPE && ZFTAPE
-config ZFT_COMPRESSOR
-        tristate
-        depends on FTAPE!=n && ZFTAPE!=n
-        default m
-config FT_NR_BUFFERS
-        int "Number of ftape buffers (EXPERIMENTAL)"
-        depends on FTAPE && EXPERIMENTAL
-        default "3"
-        help
-          Please leave this at `3' unless you REALLY know what you are doing.
-          It is not necessary to change this value. Values below 3 make the
-          proper use of ftape impossible, values greater than 3 are a waste of
-          memory. You can change the amount of DMA memory used by ftape at
-          runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
-          wastes 32 KB of memory. Please note that this memory cannot be
-          swapped out.
-config FT_PROC_FS
-        bool "Enable procfs status report (+2kb)"
-        depends on FTAPE && PROC_FS
-        ---help---
-          Optional. Saying Y will result in creation of a directory
-          `/proc/ftape' under the /proc file system. The files can be viewed
-          with your favorite pager (i.e. use "more /proc/ftape/history" or
-          "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
-          file will contain some status information about the inserted
-          cartridge, the kernel driver, your tape drive, the floppy disk
-          controller and the error history for the most recent use of the
-          kernel driver. Saying Y will enlarge the size of the ftape driver
-          by approximately 2 KB.
-          WARNING: When compiling ftape as a module (i.e. saying M to "Floppy
-          tape drive") it is dangerous to use ftape's /proc file system
-          interface. Accessing `/proc/ftape' while the module is unloaded will
-          result in a kernel Oops. This cannot be fixed from inside ftape.
-choice
-        prompt "Debugging output"
-        depends on FTAPE
-        default FT_NORMAL_DEBUG
-config FT_NORMAL_DEBUG
-        bool "Normal"
-        ---help---
-          This option controls the amount of debugging output the ftape driver
-          is ABLE to produce; it does not increase or diminish the debugging
-          level itself. If unsure, leave this at its default setting,
-          i.e. choose "Normal".
-          Ftape can print lots of debugging messages to the system console
-          resp. kernel log files. Reducing the amount of possible debugging
-          output reduces the size of the kernel module by some KB, so it might
-          be a good idea to use "None" for emergency boot floppies.
-          If you want to save memory then the following strategy is
-          recommended: leave this option at its default setting "Normal" until
-          you know that the driver works as expected, afterwards reconfigure
-          the kernel, this time specifying "Reduced" or "None" and recompile
-          and install the kernel as usual. Note that choosing "Excessive"
-          debugging output does not increase the amount of debugging output
-          printed to the console but only makes it possible to produce
-          "Excessive" debugging output.
-          Please read <file:Documentation/ftape.txt> for a short description
-          how to control the amount of debugging output.
-config FT_FULL_DEBUG
-        bool "Excessive"
-        help
-          Extremely verbose output for driver debugging purposes.
-config FT_NO_TRACE
-        bool "Reduced"
-        help
-          Reduced tape driver debugging output.
-config FT_NO_TRACE_AT_ALL
-        bool "None"
-        help
-          Suppress all debugging output from the tape drive.
-endchoice
-comment "Hardware configuration"
-        depends on FTAPE
-choice
-        prompt "Floppy tape controllers"
-        depends on FTAPE
-        default FT_STD_FDC
-config FT_STD_FDC
-        bool "Standard"
-        ---help---
-          Only change this setting if you have a special controller. If you
-          didn't plug any add-on card into your computer system but just
-          plugged the floppy tape cable into the already existing floppy drive
-          controller then you don't want to change the default setting,
-          i.e. choose "Standard".
-          Choose "MACH-2" if you have a Mountain Mach-2 controller.
-          Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
-          controller.
-          Choose "Alt/82078" if you have another controller that is located at
-          an IO base address different from the standard floppy drive
-          controller's base address of `0x3f0', or uses an IRQ (interrupt)
-          channel different from `6', or a DMA channel different from
-          `2'. This is necessary for any controller card that is based on
-          Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
-          speed" controllers.
-          If you choose something other than "Standard" then please make
-          sure that the settings for the IO base address and the IRQ and DMA
-          channel in the configuration menus below are correct. Use the manual
-          of your tape drive to determine the correct settings!
-          If you are already successfully using your tape drive with another
-          operating system then you definitely should use the same settings
-          for the IO base, the IRQ and DMA channel that have proven to work
-          with that other OS.
-          Note that this menu lets you specify only the default setting for
-          the hardware setup. The hardware configuration can be changed at
-          boot time (when ftape is compiled into the kernel, i.e. if you
-          have said Y to "Floppy tape drive") or module load time (i.e. if you
-          have said M to "Floppy tape drive").
-          Please read also the file <file:Documentation/ftape.txt> which
-          contains a short description of the parameters that can be set at
-          boot or load time. If you want to use your floppy tape drive on a
-          PCI-bus based system, please read the file
-          <file:drivers/char/ftape/README.PCI>.
-config FT_MACH2
-        bool "MACH-2"
-config FT_PROBE_FC10
-        bool "FC-10/FC-20"
-config FT_ALT_FDC
-        bool "Alt/82078"
-endchoice
-comment "Consult the manuals of your tape drive for the correct settings!"
-        depends on FTAPE && !FT_STD_FDC
-config FT_FDC_BASE
-        hex "IO base of the floppy disk controller"
-        depends on FTAPE && !FT_STD_FDC
-        default "0"
-        ---help---
-          You don't need to specify a value if the following default
-          settings for the base IO address are correct:
-          <<< MACH-2     : 0x1E0 >>>
-          <<< FC-10/FC-20: 0x180 >>>
-          <<< Secondary  : 0x370 >>>
-          Secondary refers to a secondary FDC controller like the "high speed"
-          controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
-          Please make sure that the setting for the IO base address
-          specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
-          CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
-          successfully using the tape drive with another operating system then
-          you definitely should use the same settings for the IO base that has
-          proven to work with that other OS.
-          Note that this menu lets you specify only the default setting for
-          the IO base. The hardware configuration can be changed at boot time
-          (when ftape is compiled into the kernel, i.e. if you specified Y to
-          "Floppy tape drive") or module load time (i.e. if you have said M to
-          "Floppy tape drive").
-          Please read also the file <file:Documentation/ftape.txt> which
-          contains a short description of the parameters that can be set at
-          boot or load time.
-config FT_FDC_IRQ
-        int "IRQ channel of the floppy disk controller"
-        depends on FTAPE && !FT_STD_FDC
-        default "0"
-        ---help---
-          You don't need to specify a value if the following default
-          settings for the interrupt channel are correct:
-          <<< MACH-2     : 6 >>>
-          <<< FC-10/FC-20: 9 >>>
-          <<< Secondary  : 6 >>>
-          Secondary refers to secondary a FDC controller like the "high speed"
-          controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
-          Please make sure that the setting for the IO base address
-          specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
-          CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
-          successfully using the tape drive with another operating system then
-          you definitely should use the same settings for the IO base that has
-          proven to work with that other OS.
-          Note that this menu lets you specify only the default setting for
-          the IRQ channel. The hardware configuration can be changed at boot
-          time (when ftape is compiled into the kernel, i.e. if you said Y to
-          "Floppy tape drive") or module load time (i.e. if you said M to
-          "Floppy tape drive").
-          Please read also the file <file:Documentation/ftape.txt> which
-          contains a short description of the parameters that can be set at
-          boot or load time.
-config FT_FDC_DMA
-        int "DMA channel of the floppy disk controller"
-        depends on FTAPE && !FT_STD_FDC
-        default "0"
-        ---help---
-          You don't need to specify a value if the following default
-          settings for the DMA channel are correct:
-          <<< MACH-2     : 2 >>>
-          <<< FC-10/FC-20: 3 >>>
-          <<< Secondary  : 2 >>>
-          Secondary refers to a secondary FDC controller like the "high speed"
-          controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
-          Please make sure that the setting for the IO base address
-          specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
-          CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
-          successfully using the tape drive with another operating system then
-          you definitely should use the same settings for the IO base that has
-          proven to work with that other OS.
-          Note that this menu lets you specify only the default setting for
-          the DMA channel. The hardware configuration can be changed at boot
-          time (when ftape is compiled into the kernel, i.e. if you said Y to
-          "Floppy tape drive") or module load time (i.e. if you said M to
-          "Floppy tape drive").
-          Please read also the file <file:Documentation/ftape.txt> which
-          contains a short description of the parameters that can be set at
-          boot or load time.
-config FT_FDC_THR
-        int "Default FIFO threshold (EXPERIMENTAL)"
-        depends on FTAPE && EXPERIMENTAL
-        default "8"
-        help
-          Set the FIFO threshold of the FDC. If this is higher the DMA
-          controller may serve the FDC after a higher latency time. If this is
-          lower, fewer DMA transfers occur leading to less bus contention.
-          You may try to tune this if ftape annoys you with "reduced data
-          rate because of excessive overrun errors" messages. However, this
-          doesn't seem to have too much effect.
-          If unsure, don't touch the initial value, i.e. leave it at "8".
-config FT_FDC_MAX_RATE
-        int "Maximal data rate to use (EXPERIMENTAL)"
-        depends on FTAPE && EXPERIMENTAL
-        default "2000"
-        ---help---
-          With some motherboard/FDC combinations ftape will not be able to
-          run your FDC/tape drive combination at the highest available
-          speed. If this is the case you'll encounter "reduced data rate
-          because of excessive overrun errors" messages and lots of retries
-          before ftape finally decides to reduce the data rate.
-          In this case it might be desirable to tell ftape beforehand that
-          it need not try to run the tape drive at the highest available
-          speed. If unsure, leave this disabled, i.e. leave it at 2000
-          bits/sec.
-config FT_ALPHA_CLOCK
-        int "CPU clock frequency of your DEC Alpha" if ALPHA
-        depends on FTAPE
-        default "0"
-        help
-          On some DEC Alpha machines the CPU clock frequency cannot be
-          determined automatically, so you need to specify it here ONLY if
-          running a DEC Alpha, otherwise this setting has no effect.

diff --git a/drivers/char/ftape/Kconfig b/drivers/char/ftape/Kconfig deleted file mode 100644 index 0d65189a7ae8..000000000000 --- a/drivers/char/ftape/Kconfig +++ /dev/null
@@ -1,330 +0,0 @@
1	#
2	# Ftape configuration
3	#
4	config ZFTAPE
5	tristate "Zftape, the VFS interface"
6	depends on FTAPE
7	---help---
8	Normally, you want to say Y or M. DON'T say N here or you
9	WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
10
11	The ftape module itself no longer contains the routines necessary
12	to interface with the kernel VFS layer (i.e. to actually write data
13	to and read data from the tape drive). Instead the file system
14	interface (i.e. the hardware independent part of the driver) has
15	been moved to a separate module.
16
17	To compile this driver as a module, choose M here: the
18	module will be called zftape.
19
20	Regardless of whether you say Y or M here, an additional runtime
21	loadable module called `zft-compressor' which contains code to
22	support user transparent on-the-fly compression based on Ross
23	William's lzrw3 algorithm will be produced. If you have enabled the
24	kernel module loader (i.e. have said Y to "Kernel module loader
25	support", above) then `zft-compressor' will be loaded
26	automatically by zftape when needed.
27
28	Despite its name, zftape does NOT use compression by default.
29
30	config ZFT_DFLT_BLK_SZ
31	int "Default block size"
32	depends on ZFTAPE
33	default "10240"
34	---help---
35	If unsure leave this at its default value, i.e. 10240. Note that
36	you specify only the default block size here. The block size can be
37	changed at run time using the MTSETBLK tape operation with the
38	MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
39	shell command line).
40
41	The probably most striking difference between zftape and previous
42	versions of ftape is the fact that all data must be written or read
43	in multiples of a fixed block size. The block size defaults to
44	10240 which is what GNU tar uses. The values for the block size
45	should be either 1 or multiples of 1024 up to a maximum value of
46	63488 (i.e. 62 K). If you specify `1' then zftape's builtin
47	compression will be disabled.
48
49	Reasonable values are `10240' (GNU tar's default block size),
50	`5120' (afio's default block size), `32768' (default block size some
51	backup programs assume for SCSI tape drives) or `1' (no restriction
52	on block size, but disables builtin compression).
53
54	comment "The compressor will be built as a module only!"
55	depends on FTAPE && ZFTAPE
56
57	config ZFT_COMPRESSOR
58	tristate
59	depends on FTAPE!=n && ZFTAPE!=n
60	default m
61
62	config FT_NR_BUFFERS
63	int "Number of ftape buffers (EXPERIMENTAL)"
64	depends on FTAPE && EXPERIMENTAL
65	default "3"
66	help
67	Please leave this at `3' unless you REALLY know what you are doing.
68	It is not necessary to change this value. Values below 3 make the
69	proper use of ftape impossible, values greater than 3 are a waste of
70	memory. You can change the amount of DMA memory used by ftape at
71	runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
72	wastes 32 KB of memory. Please note that this memory cannot be
73	swapped out.
74
75	config FT_PROC_FS
76	bool "Enable procfs status report (+2kb)"
77	depends on FTAPE && PROC_FS
78	---help---
79	Optional. Saying Y will result in creation of a directory
80	`/proc/ftape' under the /proc file system. The files can be viewed
81	with your favorite pager (i.e. use "more /proc/ftape/history" or
82	"less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
83	file will contain some status information about the inserted
84	cartridge, the kernel driver, your tape drive, the floppy disk
85	controller and the error history for the most recent use of the
86	kernel driver. Saying Y will enlarge the size of the ftape driver
87	by approximately 2 KB.
88
89	WARNING: When compiling ftape as a module (i.e. saying M to "Floppy
90	tape drive") it is dangerous to use ftape's /proc file system
91	interface. Accessing `/proc/ftape' while the module is unloaded will
92	result in a kernel Oops. This cannot be fixed from inside ftape.
93
94	choice
95	prompt "Debugging output"
96	depends on FTAPE
97	default FT_NORMAL_DEBUG
98
99	config FT_NORMAL_DEBUG
100	bool "Normal"
101	---help---
102	This option controls the amount of debugging output the ftape driver
103	is ABLE to produce; it does not increase or diminish the debugging
104	level itself. If unsure, leave this at its default setting,
105	i.e. choose "Normal".
106
107	Ftape can print lots of debugging messages to the system console
108	resp. kernel log files. Reducing the amount of possible debugging
109	output reduces the size of the kernel module by some KB, so it might
110	be a good idea to use "None" for emergency boot floppies.
111
112	If you want to save memory then the following strategy is
113	recommended: leave this option at its default setting "Normal" until
114	you know that the driver works as expected, afterwards reconfigure
115	the kernel, this time specifying "Reduced" or "None" and recompile
116	and install the kernel as usual. Note that choosing "Excessive"
117	debugging output does not increase the amount of debugging output
118	printed to the console but only makes it possible to produce
119	"Excessive" debugging output.
120
121	Please read <file:Documentation/ftape.txt> for a short description
122	how to control the amount of debugging output.
123
124	config FT_FULL_DEBUG
125	bool "Excessive"
126	help
127	Extremely verbose output for driver debugging purposes.
128
129	config FT_NO_TRACE
130	bool "Reduced"
131	help
132	Reduced tape driver debugging output.
133
134	config FT_NO_TRACE_AT_ALL
135	bool "None"
136	help
137	Suppress all debugging output from the tape drive.
138
139	endchoice
140
141	comment "Hardware configuration"
142	depends on FTAPE
143
144	choice
145	prompt "Floppy tape controllers"
146	depends on FTAPE
147	default FT_STD_FDC
148
149	config FT_STD_FDC
150	bool "Standard"
151	---help---
152	Only change this setting if you have a special controller. If you
153	didn't plug any add-on card into your computer system but just
154	plugged the floppy tape cable into the already existing floppy drive
155	controller then you don't want to change the default setting,
156	i.e. choose "Standard".
157
158	Choose "MACH-2" if you have a Mountain Mach-2 controller.
159	Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
160	controller.
161	Choose "Alt/82078" if you have another controller that is located at
162	an IO base address different from the standard floppy drive
163	controller's base address of `0x3f0', or uses an IRQ (interrupt)
164	channel different from `6', or a DMA channel different from
165	`2'. This is necessary for any controller card that is based on
166	Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
167	speed" controllers.
168
169	If you choose something other than "Standard" then please make
170	sure that the settings for the IO base address and the IRQ and DMA
171	channel in the configuration menus below are correct. Use the manual
172	of your tape drive to determine the correct settings!
173
174	If you are already successfully using your tape drive with another
175	operating system then you definitely should use the same settings
176	for the IO base, the IRQ and DMA channel that have proven to work
177	with that other OS.
178
179	Note that this menu lets you specify only the default setting for
180	the hardware setup. The hardware configuration can be changed at
181	boot time (when ftape is compiled into the kernel, i.e. if you
182	have said Y to "Floppy tape drive") or module load time (i.e. if you
183	have said M to "Floppy tape drive").
184
185	Please read also the file <file:Documentation/ftape.txt> which
186	contains a short description of the parameters that can be set at
187	boot or load time. If you want to use your floppy tape drive on a
188	PCI-bus based system, please read the file
189	<file:drivers/char/ftape/README.PCI>.
190
191	config FT_MACH2
192	bool "MACH-2"
193
194	config FT_PROBE_FC10
195	bool "FC-10/FC-20"
196
197	config FT_ALT_FDC
198	bool "Alt/82078"
199
200	endchoice
201
202	comment "Consult the manuals of your tape drive for the correct settings!"
203	depends on FTAPE && !FT_STD_FDC
204
205	config FT_FDC_BASE
206	hex "IO base of the floppy disk controller"
207	depends on FTAPE && !FT_STD_FDC
208	default "0"
209	---help---
210	You don't need to specify a value if the following default
211	settings for the base IO address are correct:
212	<<< MACH-2 : 0x1E0 >>>
213	<<< FC-10/FC-20: 0x180 >>>
214	<<< Secondary : 0x370 >>>
215	Secondary refers to a secondary FDC controller like the "high speed"
216	controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
217	Please make sure that the setting for the IO base address
218	specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
219	CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
220	successfully using the tape drive with another operating system then
221	you definitely should use the same settings for the IO base that has
222	proven to work with that other OS.
223
224	Note that this menu lets you specify only the default setting for
225	the IO base. The hardware configuration can be changed at boot time
226	(when ftape is compiled into the kernel, i.e. if you specified Y to
227	"Floppy tape drive") or module load time (i.e. if you have said M to
228	"Floppy tape drive").
229
230	Please read also the file <file:Documentation/ftape.txt> which
231	contains a short description of the parameters that can be set at
232	boot or load time.
233
234	config FT_FDC_IRQ
235	int "IRQ channel of the floppy disk controller"
236	depends on FTAPE && !FT_STD_FDC
237	default "0"
238	---help---
239	You don't need to specify a value if the following default
240	settings for the interrupt channel are correct:
241	<<< MACH-2 : 6 >>>
242	<<< FC-10/FC-20: 9 >>>
243	<<< Secondary : 6 >>>
244	Secondary refers to secondary a FDC controller like the "high speed"
245	controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
246	Please make sure that the setting for the IO base address
247	specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
248	CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
249	successfully using the tape drive with another operating system then
250	you definitely should use the same settings for the IO base that has
251	proven to work with that other OS.
252
253	Note that this menu lets you specify only the default setting for
254	the IRQ channel. The hardware configuration can be changed at boot
255	time (when ftape is compiled into the kernel, i.e. if you said Y to
256	"Floppy tape drive") or module load time (i.e. if you said M to
257	"Floppy tape drive").
258
259	Please read also the file <file:Documentation/ftape.txt> which
260	contains a short description of the parameters that can be set at
261	boot or load time.
262
263	config FT_FDC_DMA
264	int "DMA channel of the floppy disk controller"
265	depends on FTAPE && !FT_STD_FDC
266	default "0"
267	---help---
268	You don't need to specify a value if the following default
269	settings for the DMA channel are correct:
270	<<< MACH-2 : 2 >>>
271	<<< FC-10/FC-20: 3 >>>
272	<<< Secondary : 2 >>>
273	Secondary refers to a secondary FDC controller like the "high speed"
274	controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
275	Please make sure that the setting for the IO base address
276	specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
277	CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
278	successfully using the tape drive with another operating system then
279	you definitely should use the same settings for the IO base that has
280	proven to work with that other OS.
281
282	Note that this menu lets you specify only the default setting for
283	the DMA channel. The hardware configuration can be changed at boot
284	time (when ftape is compiled into the kernel, i.e. if you said Y to
285	"Floppy tape drive") or module load time (i.e. if you said M to
286	"Floppy tape drive").
287
288	Please read also the file <file:Documentation/ftape.txt> which
289	contains a short description of the parameters that can be set at
290	boot or load time.
291
292	config FT_FDC_THR
293	int "Default FIFO threshold (EXPERIMENTAL)"
294	depends on FTAPE && EXPERIMENTAL
295	default "8"
296	help
297	Set the FIFO threshold of the FDC. If this is higher the DMA
298	controller may serve the FDC after a higher latency time. If this is
299	lower, fewer DMA transfers occur leading to less bus contention.
300	You may try to tune this if ftape annoys you with "reduced data
301	rate because of excessive overrun errors" messages. However, this
302	doesn't seem to have too much effect.
303
304	If unsure, don't touch the initial value, i.e. leave it at "8".
305
306	config FT_FDC_MAX_RATE
307	int "Maximal data rate to use (EXPERIMENTAL)"
308	depends on FTAPE && EXPERIMENTAL
309	default "2000"
310	---help---
311	With some motherboard/FDC combinations ftape will not be able to
312	run your FDC/tape drive combination at the highest available
313	speed. If this is the case you'll encounter "reduced data rate
314	because of excessive overrun errors" messages and lots of retries
315	before ftape finally decides to reduce the data rate.
316
317	In this case it might be desirable to tell ftape beforehand that
318	it need not try to run the tape drive at the highest available
319	speed. If unsure, leave this disabled, i.e. leave it at 2000
320	bits/sec.
321
322	config FT_ALPHA_CLOCK
323	int "CPU clock frequency of your DEC Alpha" if ALPHA
324	depends on FTAPE
325	default "0"
326	help
327	On some DEC Alpha machines the CPU clock frequency cannot be
328	determined automatically, so you need to specify it here ONLY if
329	running a DEC Alpha, otherwise this setting has no effect.
330