Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 27 Feb 2003 18:38:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 27 Feb 2003 18:38:02 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:59665 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Thu, 27 Feb 2003 18:38:00 -0500 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: mem= option for broken bioses Date: 27 Feb 2003 15:48:16 -0800 Organization: Transmeta Corporation, Santa Clara CA Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2003 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1263 Lines: 31 Followup to: By author: "Grover, Andrew" In newsgroup: linux.dev.kernel > > > From: Pavel Machek [mailto:pavel@ucw.cz] > > I've seen broken bios that did not mark acpi tables in e820 > > tables. This allows user to override it. Please apply, > > OK, looks reasonable. Can you also gen up a patch documenting this in > kernel-parameters.txt? > This is very much *NOT* reasonable. In fact, screwing around with the syntax of the mem= parameter is poison. I know it has already happened, and those changes need to be reverted and the new stuff moved to a different option. The mem= option is unique in that it is an option that affects both the boot loader and the kernel. Therefore, ITS SYNTAX MUST NOT CHANGE. -hpa -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: cris ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/