From: Lukas Schrangl <schrangl-hi6Y0CQ0nG0@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Disassembling an SSDT
Date: Thu, 1 Apr 2004 08:48:32 +0200 [thread overview]
Message-ID: <200404010848.33009.schrangl@gmx.net> (raw)
In-Reply-To: <37F890616C995246BE76B3E6B2DBE0552D1295-sBd4vmA9Se7vCEQmvpVV9VDQ4js95KgL@public.gmane.org>
Am Mittwoch, 31. März 2004 21:10 schrieb Moore, Robert:
> I'm working on adding this support to iASL right now.
> It should happen either this week or next.
> Bob
>
>
> -----Original Message-----
> From: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> [mailto:acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Dino Klein
> Sent: Wednesday, March 31, 2004 10:42 AM
> To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> Subject: [ACPI] Disassembling an SSDT
>
> Hi,
> I'm having difficulties disassembling an SSDT via Intel's ASL compiler -
> it fails with unresolved references, since the SSDT is attempting to add
> methods to the Processor object declared in the SSDT.
> I couldn't find any switches that will get iasl to complete successfuly,
> and using the disassembler in the old pmtools package generates a very
> unreadable output.
> Any help is much appreciated.
> Thanks.
>
Using old acpidisasm workes (look for an old version of pmtools).
Lukas
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=Click
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
next prev parent reply other threads:[~2004-04-01 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 19:10 Disassembling an SSDT Moore, Robert
[not found] ` <37F890616C995246BE76B3E6B2DBE0552D1295-sBd4vmA9Se7vCEQmvpVV9VDQ4js95KgL@public.gmane.org>
2004-04-01 6:48 ` Lukas Schrangl [this message]
[not found] ` <200404010848.33009.schrangl-hi6Y0CQ0nG0@public.gmane.org>
2004-04-01 7:09 ` Lukas Schrangl
-- strict thread matches above, loose matches on Subject: below --
2004-03-31 18:42 Dino Klein
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=200404010848.33009.schrangl@gmx.net \
--to=schrangl-hi6y0cq0ng0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.