public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralph Blach <chipper-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: problems with acpi_tb_validate_rsdt
Date: Fri, 10 Jun 2005 14:41:03 -0400	[thread overview]
Message-ID: <42A9DEBF.5040404@us.ibm.com> (raw)

Guys,

I have a problem.  I have a bios ACPI 2.0 level Bios that has RSDT table 
  but NO xsdt table.  This is allowed in the spec,

If you have no XSDT table, then you are to use the RSDT table.

If you have both, then it is required that you use the XSDT table, not 
make a copy of the XSDT from the RSDT table.


Look on page 98 of   ACPIspec-2-0c where  it says that


"5.2.7 Extended System Description Table (XSDT)

The XSDT provides identical functionality to the RSDT but accommodates 
physical addresses of
DESCRIPTION HEADERs that are larger than 32-bits. Notice that both the 
XSDT and the RSDT can be
pointed to by the RSDP structure. An ACPI 2.0-compatible OS must use the 
XSDT if present."

as it is now, with no XSDT table, the search for the RSDT simple walks 
memory and fails

Also, if the XSDT table is present, it appears to be deleted and NOT 
used.  This is incorrect.  It MUST be used over the RSDT.

Any comments on how to fix?

Good, bad, am I wrong? I am open to comments,


Chip
-- 
Ralph "Chip" Blach
chipper-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
IBM Linux Technology Center
Raleigh, North Carolina
919 543 1207


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20

                 reply	other threads:[~2005-06-10 18:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=42A9DEBF.5040404@us.ibm.com \
    --to=chipper-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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