Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1450472 > unrolled thread

[PATCH] README: Mention when 386 support ended + update obsolete 386 paths

Back to article view | Back to linux.kernel

Contents

  [PATCH] README: Mention when 386 support ended + update obsolete 386 paths Øyvind A. Holm <sunny@sunbase.org> - 2016-07-26 10:30 +0200
    Re: [PATCH] README: Mention when 386 support ended + update  obsolete 386 paths Jonathan Corbet <corbet@lwn.net> - 2016-07-26 14:20 +0200
      Re: [PATCH] README: Mention when 386 support ended + update obsolete  386 paths Øyvind A. Holm <sunny@sunbase.org> - 2016-07-26 15:00 +0200
      Re: [PATCH] README: Mention when 386 support ended + update obsolete  386 paths Pavel Machek <pavel@ucw.cz> - 2016-08-05 11:30 +0200

#1450472 — [PATCH] README: Mention when 386 support ended + update obsolete 386 paths

The paragraph about i386 could be misinterpreted as if 386 still is a
valid processor type. Mention when 386 support ended, and change two
"arch/i386/" paths to one that exists, "arch/x86/".

Signed-off-by: Øyvind A. Holm <sunny@sunbase.org>
---
 README | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/README b/README
index e8c8a6d..2c5c125 100644
--- a/README
+++ b/README
@@ -231,7 +231,8 @@ CONFIGURING the kernel:
 
     - 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.
+      kernel will detect this on bootup, and give up. The last kernel
+      with support for 386 was version 3.7.
 
     - A kernel with math-emulation compiled in will still use the
       coprocessor if one is present: the math emulation will just
@@ -289,7 +290,7 @@ COMPILING the kernel:
    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 +392,7 @@ IF SOMETHING GOES WRONG:
 
  - 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".
-- 
2.9.2.466.g8c6d1f9

[toc] | [next] | [standalone]

#1450559 — Re: [PATCH] README: Mention when 386 support ended + update obsolete 386 paths

On Tue, 26 Jul 2016 09:45:43 +0200
Øyvind A. Holm <sunny@sunbase.org> wrote:

>      - 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.
> +      kernel will detect this on bootup, and give up. The last kernel
> +      with support for 386 was version 3.7.

So we want the documentation to reflect current kernels, not those from
years gone by.  I can't think of a reason why this paragraph should
continue to exist at all.  Can you make a new version that removes it
altogether?

Thanks,

jon

[toc] | [prev] | [next] | [standalone]

#1450591 — Re: [PATCH] README: Mention when 386 support ended + update obsolete 386 paths

On 26 July 2016 at 14:12, Jonathan Corbet <corbet@lwn.net> wrote:
> On Tue, 26 Jul 2016 09:45:43 +0200 Øyvind A. Holm <sunny@sunbase.org>
> wrote:
> > - 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.
> > + kernel will detect this on bootup, and give up. The last kernel
> > + with support for 386 was version 3.7.
>
> So we want the documentation to reflect current kernels, not those
> from years gone by.  I can't think of a reason why this paragraph
> should continue to exist at all.  Can you make a new version that
> removes it altogether?

That was also my first thought, yes. But then I thought, maybe there's
some value to that information in case someone wants to try a new kernel
on some ancient hardware. But it's probably an unlikely scenario. I'll
send a new patch now.

        Øyvind

[toc] | [prev] | [next] | [standalone]

#1456978 — Re: [PATCH] README: Mention when 386 support ended + update obsolete 386 paths

On Tue 2016-07-26 06:12:29, Jonathan Corbet wrote:
> On Tue, 26 Jul 2016 09:45:43 +0200
> Øyvind A. Holm <sunny@sunbase.org> wrote:
> 
> >      - 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.
> > +      kernel will detect this on bootup, and give up. The last kernel
> > +      with support for 386 was version 3.7.
> 
> So we want the documentation to reflect current kernels, not those from
> years gone by.  I can't think of a reason why this paragraph should
> continue to exist at all.  Can you make a new version that removes it
> altogether?

You may want to generalize it to "will not boot if you se processor
type too high", but I'd keep v3.7 note -- it is going to be tricky to
find out in any other way.

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web