From: Lin Ming <ming.m.lin@intel.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
"hmh@hmh.eng.br" <hmh@hmh.eng.br>,
"Moore, Robert" <robert.moore@intel.com>
Subject: Re: iasl and SSDT disassembling limitations
Date: Thu, 30 Oct 2008 17:16:50 +0800 [thread overview]
Message-ID: <1225358210.4477.52.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <200810301011.37320.elendil@planet.nl>
On Thu, 2008-10-30 at 17:11 +0800, Frans Pop wrote:
> On Friday 24 October 2008, Lin Ming wrote:
> > We have added a "-e" option to iasl that include tables for external
> > symbol resolution.
>
> Thanks very much. That does indeed give me a correctly disassembled table.
>
> Would it be possible to add a warning when unavailable external symbols
> are detected? The warning could even be made verbose by saying that this
> may result in an incorrect dsl file and refer to the -e option (and maybe
> even specifically mention the dsdt table if that is the source for
> missing symbols in most cases).
Good idea. Yes, we are going to add this warning message.
Lin Ming
>
> Currently there is really no indication at all that something may have
> gone wrong or why until you look at the generated dsl file.
>
> Cheers,
> FJP
next prev parent reply other threads:[~2008-10-30 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3515468CA27A0F49917112E2ECF61E210927CBF912@pdsmsx502.ccr.corp.intel.com>
2008-10-24 10:50 ` iasl and SSDT disassembling limitations Lin Ming
2008-10-30 9:11 ` Frans Pop
2008-10-30 9:16 ` Lin Ming [this message]
2008-11-13 0:17 ` Thomas Renninger
2008-11-13 7:02 ` Lin Ming
2008-11-14 16:28 ` Thomas Renninger
2008-11-18 7:53 ` Lin Ming
2008-11-18 8:00 ` Lin Ming
2008-09-25 9:19 Syntax errors in SSDT1 table of HP 2510p laptop Frans Pop
2008-09-26 3:44 ` Zhao Yakui
2008-09-26 4:52 ` Frans Pop
2008-09-26 13:37 ` Moore, Robert
2008-09-26 16:08 ` iasl and SSDT disassembling limitations Henrique de Moraes Holschuh
2008-09-26 16:48 ` 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=1225358210.4477.52.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=elendil@planet.nl \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=robert.moore@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