From: Alex Williamson <alex.williamson@hp.com>
To: "Yu, Luming" <luming.yu@intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
acpi-devel@lists.sourceforge.net, "Brown,
Len" <len.brown@intel.com>
Subject: RE: [ACPI] [PATCH] 2.4/2.6 use xdsdt to print table header
Date: Tue, 13 Jan 2004 08:28:46 -0700 [thread overview]
Message-ID: <1074007725.6494.11.camel@patsy.fc.hp.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720CC2@PDSMSX403.ccr.corp.intel.com>
On Tue, 2004-01-13 at 00:38, Yu, Luming wrote:
> > I'm resending this patch to get it into the main ACPI source. This
> > fixes a problem where the DSDT pointer in the FADT is NULL because it
> > uses the 64bit XDSDT instead. The current code is happy to map a NULL
> > address and return success to the caller. This can crash the
> > system or
> > printout garbage headers to the console. It's a simple
> > matter to check
> > table revision and use the XDSDT in favor of the DSDT. This has been
> > living happily in both the 2.4 and 2.6 ia64 tree for some
> > time. Please
> > accept. Thanks,
>
> I just checked with http://lia64.bkbits.net:8080/linux-ia64-2.4 .
> The patch has been merged. Please take a look at
Right, it's in the ia64 trees, but understandably the ia64 arch
maintainers don't want to carry this non-ia64 specific patch
indefinitely. This is a generic ACPI issue for an system that chooses
to use the xdsdt in place of the dsdt. It should be included in the
ACPI tree and pushed up from there. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
next prev parent reply other threads:[~2004-01-13 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 7:38 [ACPI] [PATCH] 2.4/2.6 use xdsdt to print table header Yu, Luming
2004-01-13 15:28 ` Alex Williamson [this message]
2004-01-18 2:41 Yu, Luming
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=1074007725.6494.11.camel@patsy.fc.hp.com \
--to=alex.williamson@hp.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).