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>

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>
Øyvind A. Holm · Jonathan Corbet
1 parent 6203a64278
Showing 1 changed file with 2 additions and 6 deletions Side-by-side Diff
README
@@ -229,10 +229,6 @@
       under some circumstances lead to problems: probing for a
       nonexistent controller card may confuse your other controllers
  
-    - Compiling the kernel with "Processor type" set higher than 386
-      will result in a kernel that does NOT work on a 386.  The
-      kernel will detect this on bootup, and give up.
-
     - A kernel with math-emulation compiled in will still use the
       coprocessor if one is present: the math emulation will just
       never get used in that case.  The kernel will be slightly larger,
@@ -289,7 +285,7 @@
    LOCALVERSION can be set in the "General Setup" menu.
  
  - In order to boot your new kernel, you'll need to copy the kernel
-   image (e.g. .../linux/arch/i386/boot/bzImage after compilation)
+   image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
    to the place where your regular bootable kernel is found.
  
  - Booting a kernel directly from a floppy without the assistance of a
@@ -391,7 +387,7 @@
  
  - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
    cannot change values or set break points.) To do this, first compile the
-   kernel with -g; edit arch/i386/Makefile appropriately, then do a "make
+   kernel with -g; edit arch/x86/Makefile appropriately, then do a "make
    clean". You'll also need to enable CONFIG_PROC_FS (via "make config").
  
    After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".
...	...	@@ -229,10 +229,6 @@
229	229	under some circumstances lead to problems: probing for a
230	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	232	- A kernel with math-emulation compiled in will still use the
237	233	coprocessor if one is present: the math emulation will just
238	234	never get used in that case. The kernel will be slightly larger,
...	...	@@ -289,7 +285,7 @@
289	285	LOCALVERSION can be set in the "General Setup" menu.
290	286
291	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	289	to the place where your regular bootable kernel is found.
294	290
295	291	- Booting a kernel directly from a floppy without the assistance of a
...	...	@@ -391,7 +387,7 @@
391	387
392	388	- Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
393	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	391	clean". You'll also need to enable CONFIG_PROC_FS (via "make config").
396	392
397	393	After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".