ft_tracings=TR0,TR1,TR2,TR3,GT
|
Specify the trace levels for the ftape devices. TR0 to TR3
correspond to the debugging message that are produced by each of the
ftape devices `/dev/qft0 ' to `/dev/qft3 ' while GT
(General Trace-level) sets the trace level for messages that can't
be mapped to a specific device. TR#X is a decimal number which
controls the verbosity of the driver in the following manner:
0
|
print bugs
|
1
|
+ errors
|
2
|
+ warnings
|
3
|
+ information
|
4
|
+ more information
|
5
|
+ program flow
|
6
|
+ fdc/dma info
|
7
|
+ data flow
|
8
|
+ everything else
|
It is also possible to tune the amount of debugging output at run-time
(see MTSETDENSITY) as well as to set a limit to the amount of
debugging output ftape is able to produce at all
(see TRACE_FLAGS).
|
ft_fdc_driver=DRV0,DRV1,DRV2,DRV3
|
Define which FDC driver to use for which ftape device. DRV0
to DRV3 are strings which serve as identifiers for the FDC drivers
and are passed as argument to the kernel's module auto-loading mechanism
and thus simply give the module name of the FDC module.
In short, DRV#X should be one out of `ftape-internal ',
`trakker ' or `bpck-fdc '. In case you don't know which driver
to use, you can specify multiple drivers per device by separating them
with a colon. An example parameter specification for using the
ftape-internal module for `/dev/qft0 ' and the trakker
or bpck-fdc module for `/dev/qft1 ' would look like follows
-
ft_fdc_driver=ftape-internal,trakker:bpck,none,none
The special keyword `none ' serves to disable the devices
`/dev/qft2 ' and `/dev/qft3 '. One could pass any string except
the name of an existing module, but the special name `none '
prevents ftape from passing the parameter to the kernel
module auto-loading mechanism.
If you leave the FDC driver specification for the third and fourth
device blank like so
-
ft_fdc_driver=ftape-internal,trakker:bpck
then ftape module will try all already loaded FDC drivers for
`/dev/qft2 ' and `/dev/qft3 ' as well, searching for additional
tape drives. The same affect is achieved by passing the special keyword
`auto ' as FDC driver name, or by passing the empty string.
|