aboutsummaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorØyvind A. Holm <sunny@sunbase.org>2016-07-26 09:21:33 -0400
committerJonathan Corbet <corbet@lwn.net>2016-08-14 14:24:56 -0400
commit35db7e94cdee495673360f449cdae726d5576ab7 (patch)
tree66652fa48d6bc8765bde56b1f697f557b5e3d6b2 /README
parent6203a642785a7979ec64406da0b452037df31e75 (diff)
README: Delete obsolete i386 info + update arch/i386/ paths
Support for i386 was removed in v3.8, delete the paragraph that says processor types above 386 won't work on that architecture. It's obsolete information and potentially confusing. Also change a couple of "arch/i386/" paths to one that exists now, using "arch/x86/" instead. Signed-off-by: Øyvind A. Holm <sunny@sunbase.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'README')
-rw-r--r--README8
1 files changed, 2 insertions, 6 deletions
diff --git a/README b/README
index e8c8a6dc1c2b..09f34f78f2bb 100644
--- a/README
+++ b/README
@@ -229,10 +229,6 @@ CONFIGURING the kernel:
229 under some circumstances lead to problems: probing for a 229 under some circumstances lead to problems: probing for a
230 nonexistent controller card may confuse your other controllers 230 nonexistent controller card may confuse your other controllers
231 231
232 - Compiling the kernel with "Processor type" set higher than 386
233 will result in a kernel that does NOT work on a 386. The
234 kernel will detect this on bootup, and give up.
235
236 - A kernel with math-emulation compiled in will still use the 232 - A kernel with math-emulation compiled in will still use the
237 coprocessor if one is present: the math emulation will just 233 coprocessor if one is present: the math emulation will just
238 never get used in that case. The kernel will be slightly larger, 234 never get used in that case. The kernel will be slightly larger,
@@ -289,7 +285,7 @@ COMPILING the kernel:
289 LOCALVERSION can be set in the "General Setup" menu. 285 LOCALVERSION can be set in the "General Setup" menu.
290 286
291 - In order to boot your new kernel, you'll need to copy the kernel 287 - In order to boot your new kernel, you'll need to copy the kernel
292 image (e.g. .../linux/arch/i386/boot/bzImage after compilation) 288 image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
293 to the place where your regular bootable kernel is found. 289 to the place where your regular bootable kernel is found.
294 290
295 - Booting a kernel directly from a floppy without the assistance of a 291 - Booting a kernel directly from a floppy without the assistance of a
@@ -391,7 +387,7 @@ IF SOMETHING GOES WRONG:
391 387
392 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you 388 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
393 cannot change values or set break points.) To do this, first compile the 389 cannot change values or set break points.) To do this, first compile the
394 kernel with -g; edit arch/i386/Makefile appropriately, then do a "make 390 kernel with -g; edit arch/x86/Makefile appropriately, then do a "make
395 clean". You'll also need to enable CONFIG_PROC_FS (via "make config"). 391 clean". You'll also need to enable CONFIG_PROC_FS (via "make config").
396 392
397 After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore". 393 After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".