From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755213AbcGZI3m (ORCPT ); Tue, 26 Jul 2016 04:29:42 -0400 Received: from sunbase.org ([178.79.142.16]:33842 "EHLO sunbase" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753895AbcGZI3j (ORCPT ); Tue, 26 Jul 2016 04:29:39 -0400 X-Greylist: delayed 2604 seconds by postgrey-1.27 at vger.kernel.org; Tue, 26 Jul 2016 04:29:39 EDT From: =?UTF-8?q?=C3=98yvind=20A=2E=20Holm?= To: linux-kernel@vger.kernel.org Cc: Jonathan Corbet , Diego Viola , =?UTF-8?q?=C3=98yvind=20A=2E=20Holm?= , Jiri Kosina , Vineet Gupta Subject: [PATCH] README: Mention when 386 support ended + update obsolete 386 paths Date: Tue, 26 Jul 2016 09:45:43 +0200 Message-Id: <20160726074543.21311-1-sunny@sunbase.org> X-Mailer: git-send-email 2.9.2.466.g8c6d1f9 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 --- 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