From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755540AbcGZNWB (ORCPT ); Tue, 26 Jul 2016 09:22:01 -0400 Received: from sunbase.org ([178.79.142.16]:35076 "EHLO sunbase" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752930AbcGZNWA (ORCPT ); Tue, 26 Jul 2016 09:22:00 -0400 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 v2] README: Delete obsolete i386 info + update arch/i386/ paths Date: Tue, 26 Jul 2016 15:21:33 +0200 Message-Id: <20160726132133.21535-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 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 --- README | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/README b/README index e8c8a6d..09f34f7 100644 --- a/README +++ b/README @@ -229,10 +229,6 @@ CONFIGURING the kernel: 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 @@ 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 +387,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