archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <>
To: Romit Dasgupta <>
Cc: Linux Kernel Mailing List <>
Subject: Re: Trivial Change (E820map) : arch/i386/boot/setup.S
Date: 16 Jul 2003 19:18:10 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mer, 2003-07-16 at 18:33, Romit Dasgupta wrote:
> Hi,
>       After reading the e820 method from Ralf Brown's interrupt list(
> it seems that the es register wont get thrashed. So there is no need to 
> repatedly execute (for getting each map entry) the following two lines 
> inside jmpe820: of seutp.S and thus can be moved out as below.  Is there 
> any reason to do it inside?

Yes - BIOSes and the specification are only distant relatives. We get
all sorts of fun from them - 0 sized regions, system ROM reported as
RAM, E801 returns in the wrong registers and so on

      reply	other threads:[~2003-07-16 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16 17:33 Trivial Change (E820map) : arch/i386/boot/setup.S Romit Dasgupta
2003-07-16 18:18 ` Alan Cox [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).