All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mem= option for broken bioses
Date: Tue, 04 Mar 2003 06:21:37 -0800	[thread overview]
Message-ID: <3E64B671.4010504@zytor.com> (raw)
In-Reply-To: <20030304131855.GE618@zaurus.ucw.cz>

Pavel Machek wrote:
> 
> This should be commented, somewhere.

It's commented in Documentation/i386/boot.txt as well as the 
kernel-options file.  *ALL* i386 boot loaders need to obey this, 
unfortunately, because of how the initrd protocol was defined.

> Why is mem= option used by boot loader?
> Does your bootloader really parse stuff
> like mem=exactmap?

No, and that's exactly the problem.  A whole bunch of crap was added to 
mem= retroactively (over my explicit objections), and that broke the 
boot protocol.

	-hpa


  reply	other threads:[~2003-03-04 14:11 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
     [not found] ` <b3m840_5e4_1@cesium.transmeta.com>
2003-03-04 13:18   ` Pavel Machek
2003-03-04 14:21     ` H. Peter Anvin [this message]
  -- 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=3E64B671.4010504@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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.