From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: mem= option for broken bioses
Date: 27 Feb 2003 15:48:16 -0800 [thread overview]
Message-ID: <b3m840$5e4$1@cesium.transmeta.com> (raw)
In-Reply-To: F760B14C9561B941B89469F59BA3A8471380D7@orsmsx401.jf.intel.com
Followup to: <F760B14C9561B941B89469F59BA3A8471380D7@orsmsx401.jf.intel.com>
By author: "Grover, Andrew" <andrew.grover@intel.com>
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
--
<hpa@transmeta.com> at work, <hpa@zytor.com> 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
next prev parent reply other threads:[~2003-02-27 23:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 22:39 mem= option for broken bioses Grover, Andrew
2003-02-26 22:39 ` Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A8471380D7-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-02-26 22:44 ` Pavel Machek
2003-02-26 22:44 ` Pavel Machek
[not found] ` <20030226224450.GD15455-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2003-02-27 14:27 ` [ACPI] " Robert Woerle Paceblade/Support
2003-02-27 14:27 ` Robert Woerle Paceblade/Support
[not found] ` <3E5E2061.2060807-fPtsKRK0pHxl57MIdRCFDg@public.gmane.org>
2003-02-27 15:19 ` Pavel Machek
2003-02-27 15:19 ` Pavel Machek
[not found] ` <20030227151907.GC12434-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2003-02-27 15:49 ` Ducrot Bruno
2003-02-27 15:49 ` Ducrot Bruno
[not found] ` <20030227154922.GY13404-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-02-27 16:12 ` Pavel Machek
2003-02-27 16:12 ` Pavel Machek
2003-02-27 15:53 ` Robert Woerle Paceblade/Support
2003-02-27 15:53 ` Robert Woerle Paceblade/Support
[not found] ` <3E5E3483.7000302-fPtsKRK0pHxl57MIdRCFDg@public.gmane.org>
2003-02-27 16:16 ` Pavel Machek
2003-02-27 16:16 ` Pavel Machek
2003-02-27 23:48 ` H. Peter Anvin [this message]
[not found] ` <b3m840_5e4_1@cesium.transmeta.com>
2003-03-04 13:18 ` Pavel Machek
2003-03-04 14:21 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 20:38 Pavel Machek
2003-02-26 20:38 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='b3m840$5e4$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.