bootparam.7: Remove crufty "General non-device-specific boot arguments" options

[Part of a general change to remove cruft from this page.]
Much of the detail on hardware 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.)
Here, we remove some ancient x86 options.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2015-04-24 12:13:34 +02:00
parent 9b84d6e147
commit 0b32bd2cf2
1 changed files with 0 additions and 26 deletions

View File

@ -123,32 +123,6 @@ does not begin with '/' or ',' or a digit, then it is prefixed by
\&'/tftpboot/'.
This root name is used in case of a net boot.
.TP
.B "'no387'"
(Only when
.B CONFIG_BUGi386
is defined.)
Some i387 coprocessor chips have bugs that show up when used in 32 bit
protected mode.
For example, some of the early ULSI-387 chips would
cause solid lockups while performing floating-point calculations.
Using the 'no387' boot argument causes Linux to ignore the maths
coprocessor even if you have one.
Of course you must then have your
kernel compiled with math emulation support!
.TP
.B "'no-hlt'"
(Only when
.B CONFIG_BUGi386
is defined.)
Some of the early i486DX-100 chips have a problem with the 'hlt'
instruction, in that they can't reliably return to operating mode
after this instruction is used.
Using the 'no-hlt' instruction tells
Linux to just run an infinite loop when there is nothing else to do,
and to not halt the CPU.
This allows people with these broken chips
to use Linux.
.TP
.B "'root=...'"
This argument tells the kernel what device is to be used as the root
filesystem while booting.