public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
To: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	"Udo A. Steinberg"
	<us15-IG//nw+yl+iQIjdd1DhZXWfrygkm6VTR@public.gmane.org>
Subject: Re: Fw: [PATCH]: Correctly locate RSDP in EBDA
Date: Tue, 26 Jul 2005 10:53:57 +0100	[thread overview]
Message-ID: <1122371637.1101.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20050725151313.730257bd.akpm-3NddpPZAyC0@public.gmane.org>

On Llu, 2005-07-25 at 15:13 -0700, Andrew Morton wrote:
>          * Scan memory looking for the RSDP signature. First search EBDA (low
>          * memory) paragraphs and then search upper memory (E0000-FFFFF).
>          */
> -       rsdp_phys = acpi_scan_rsdp (0, 0x400);
> +       rsdp_phys = acpi_scan_rsdp (*(u16*) 0x40E << 4, 0x400);

Close but no cookie. You need to read 0x40E from physical memory not
kernel virtual address space. It may also be zero which indicates that
there isn't an EBDA, sometimes interpreted as an EBDA in the top 1K or
so.




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

  parent reply	other threads:[~2005-07-26  9:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 22:13 Fw: [PATCH]: Correctly locate RSDP in EBDA Andrew Morton
     [not found] ` <20050725151313.730257bd.akpm-3NddpPZAyC0@public.gmane.org>
2005-07-26  9:53   ` Alan Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-25 22:19 Moore, Robert

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=1122371637.1101.12.camel@localhost.localdomain \
    --to=alan-qbu/x9rampvanceybjwyrvxrex20p6io@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=akpm-3NddpPZAyC0@public.gmane.org \
    --cc=us15-IG//nw+yl+iQIjdd1DhZXWfrygkm6VTR@public.gmane.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