Re: [PATCH] doc/kernel-parameters: use IA-32 tag instead of i386

From: Randy Dunlap
Date: Thu Apr 05 2007 - 12:00:34 EST


Alan Cox wrote:
Alan wrote:
| NAK. IA-32 is an Intel specific term, and I believe a protected mark at
| that.

OMG, quick, please send a patch for Documentation/kernel-parameters.txt.
(big ;)


Its a lot simpler to use sed. Can't find IA32 as a mark, seems the Itanic
one was but not that. X86-32 is more consistent and not Intel specific so
one search and waste later (plus a line move)

Yep, thanks, looks good to me. However, you say "Can't find IA32 as a mark",
but it's used in a couple of places that should also be changed:

code_bytes [IA32] How many bytes of object code to print in an
oops report.
Range: 0 - 8192
Default: 64

and

disable_8254_timer
enable_8254_timer
[IA32/X86_64] Disable/Enable interrupt 0 timer routing
over the 8254 in addition to over the IO-APIC. The
kernel tries to set a sensible default.


Signed-off-by: Alan Cox <alan@xxxxxxxxxx> [not that a mechanistic conversion has any rights associated with it]

--- Documentation/kernel-parameters.txt~ 2007-04-05 16:30:30.817515360 +0100
+++ Documentation/kernel-parameters.txt 2007-04-05 16:30:30.824514296 +0100
@@ -41,7 +41,6 @@
EIDE EIDE/ATAPI support is enabled.
FB The frame buffer device is enabled.
HW Appropriate hardware is enabled.
- IA-32 IA-32 aka i386 architecture is enabled.
IA-64 IA-64 architecture is enabled.
IOSCHED More than one I/O scheduler is enabled.
IP_PNP IP DHCP, BOOTP, or RARP is enabled.
@@ -91,6 +90,7 @@
VT Virtual terminal support is enabled.
WDT Watchdog support is enabled.
XT IBM PC/XT MFM hard disk support is enabled.
+ X86-32 X86-32, aka i386 architecture is enabled.
X86-64 X86-64 architecture is enabled.
More X86-64 boot options can be found in
Documentation/x86_64/boot-options.txt .


--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/