aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2015-04-24 10:35:30 +0200
committerMichael Kerrisk <mtk.manpages@gmail.com>2015-04-24 13:46:02 +0200
commit3dd80946f8632d3d082c2e76adb1135e9829c423 (patch)
treec11ec9ed446cbed71c7c5c0e5ac813671a76a46f
parentcb6cb8608ab887ec7087cf59080be7acd28b1c73 (diff)
downloadman-pages-3dd80946f8632d3d082c2e76adb1135e9829c423.tar.gz
bootparam.7: Remove crufty floppy disk driver options
[Part of a general change to remove cruft from this page.] Much of the detail on device-driver specifics in this page dates from the 20th century. (The last major update to this page was in man-pages-1.14!) It's hugely out of date now (many of these devices disappeared from the kernel years ago.) Arguably, this kind of detail should never have been placed in a man page to begin with, since devices come and go. Remove such text, and where appropriate and possible add pointers to files in the kernel Documentation/ directory. In the specific case of floppy drives: the drivers still exist, but it's been a while since most of saw these devices in the wild. So, just refer the reader to the kernel source file for details. (The detail in this man page was after all originally drawn from that file.) Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man7/bootparam.773
1 files changed, 1 insertions, 72 deletions
diff --git a/man7/bootparam.7 b/man7/bootparam.7
index 36d5543e01..c78ca55169 100644
--- a/man7/bootparam.7
+++ b/man7/bootparam.7
@@ -765,78 +765,7 @@ There are many floppy driver options, and they are all listed in
in oplder kernels, or
.I drivers/block/README.fd
for ancient kernels) in the Linux kernel source.
-This information is taken directly
-from that file.
-.TP
-.B "floppy=mask,allowed_drive_mask"
-Sets the bit mask of allowed drives to mask.
-By default, only units 0
-and 1 of each floppy controller are allowed.
-This is done because
-certain nonstandard hardware (ASUS PCI motherboards) mess up the
-keyboard when accessing units 2 or 3.
-This option is somewhat
-obsoleted by the cmos option.
-.TP
-.B "floppy=all_drives"
-Sets the bit mask of allowed drives to all drives.
-Use this if you have
-more than two drives connected to a floppy controller.
-.TP
-.B "floppy=asus_pci"
-Sets the bit mask to allow only units 0 and 1.
-(The default)
-.TP
-.B "floppy=daring"
-Tells the floppy driver that you have a well behaved floppy
-controller.
-This allows more efficient and smoother operation, but
-may fail on certain controllers.
-This may speed up certain operations.
-.TP
-.B "floppy=0,daring"
-Tells the floppy driver that your floppy controller should be used
-with caution.
-.TP
-.B "floppy=one_fdc"
-Tells the floppy driver that you have only floppy controller (default)
-.TP
-.BR floppy=two_fdc " or " floppy=address,two_fdc
-Tells the floppy driver that you have two floppy controllers.
-The second floppy controller is assumed to be at address.
-If address is
-not given, 0x370 is assumed.
-.TP
-.B "floppy=thinkpad"
-Tells the floppy driver that you have a Thinkpad.
-Thinkpads use an
-inverted convention for the disk change line.
-.TP
-.B "floppy=0,thinkpad"
-Tells the floppy driver that you don't have a Thinkpad.
-.TP
-.B "floppy=drive,type,cmos"
-Sets the cmos type of drive to type.
-Additionally, this drive is
-allowed in the bit mask.
-This is useful if you have more than two
-floppy drives (only two can be described in the physical cmos), or if
-your BIOS uses nonstandard CMOS types.
-Setting the CMOS to 0 for the
-first two drives (default) makes the floppy driver read the physical
-cmos for those drives.
-.TP
-.B "floppy=unexpected_interrupts"
-Print a warning message when an unexpected interrupt is received
-(default behavior)
-.TP
-.BR floppy=no_unexpected_interrupts " or " floppy=L40SX
-Don't print a message when an unexpected interrupt is received.
-This is needed on IBM L40SX laptops in certain video modes.
-(There seems to
-be an interaction between video and floppy.
-The unexpected interrupts
-only affect performance, and can safely be ignored.)
+See that file for the details.
.SS The sound driver
The sound driver can also accept boot arguments to override the compiled in
values.