public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86 Boot enhancements, boot protocol 2.04 7/9
Date: Thu, 04 Apr 2002 11:19:38 -0800	[thread overview]
Message-ID: <3CACA74A.1000004@zytor.com> (raw)
In-Reply-To: <m1ofh0spik.fsf@frodo.biederman.org>	<a8flgc$ms2$1@cesium.transmeta.com>	<m1lmc3qtaz.fsf@frodo.biederman.org> <3CAC9BD4.5050500@zytor.com> <m1hemrqo9b.fsf@frodo.biederman.org>

Eric W. Biederman wrote:
>
>>There can't be a "default load address".  0x90000 is actively dangerous and
>>trying to encourage it for anything than legacy kernels is WRONG. If you can't
>>handle this, then you need to go back to the drawing board.
> 
> 
> I agree.  But I do think being able to hard code the load address is a
> very good thing.
> 
> After digesting the requirements I plan on having setup.S call int 12h
> (so the information is available), and then having misc.c relocate the
> real mode code, and the command line, out of the way, of it's
> decompression buffer.  This removes the need for bootloaders to
> make a tradeoff between memory use efficiency and reliability.
> 
> This should give me about 630KB on machines designed to run DOS, where
> this matters.   Better than the current best of 572KB, with the real
> mode code @ 0x90000. 
> 
> And when your total size is 1-4MB.  +-640KB is a significant change.
> 

Agreed.  Note that so far putting the real mode code *above* 0x90000 is 
completely untested.  It *should* work with boot protocol 2.02 support; 
it almost certainly *does not* work with earlier boot protocols (due to 
the "move it back to 0x90000" braindamage.)

	-hpa


  reply	other threads:[~2002-04-04 19:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 16:41 [PATCH] x86 Boot enhancements, boot protocol 2.04 7/9 Eric W. Biederman
2002-04-03 19:15 ` Tom Rini
2002-04-04  3:23   ` Eric W. Biederman
2002-04-04 14:10     ` Tom Rini
2002-04-04 15:38       ` Eric W. Biederman
2002-04-03 19:34 ` H. Peter Anvin
2002-04-04 17:15   ` Eric W. Biederman
2002-04-04 18:30     ` H. Peter Anvin
2002-04-04 19:04       ` Eric W. Biederman
2002-04-04 19:19         ` H. Peter Anvin [this message]
2002-04-04 19:32           ` Eric W. Biederman
2002-04-05 21:30           ` Eric W. Biederman
2002-04-05 22:04             ` H. Peter Anvin

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=3CACA74A.1000004@zytor.com \
    --to=hpa@zytor.com \
    --cc=ebiederm@xmission.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox