From: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
To: Voluspa <voluspa-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: acpidump replaces acpidmp
Date: Wed, 27 Jul 2005 17:05:09 +0200 [thread overview]
Message-ID: <42E7A2A5.3040103@suse.de> (raw)
In-Reply-To: <20050727154458.455d16db.voluspa-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org>
Voluspa wrote:
> 24 -r-------- 1 root root 24136 Jul 27 14:47 dsdt
> 28 -rw-r--r-- 1 root root 24743 Jul 27 14:52 dsdt.acpidump
>
> OK, I now know that acpidump gives me both fadt and dsdt and something
> more, hence the difference. But this is usability madness; 1) The
> documentation of program switches, Both README and source, swing between
> mildly accurate and inaccurate; 2) Having to dump/decode in several
> steps here (not really knowing if you've made an error) and then later
> in iasl as well.
>
> Compared to just copying dsdt from /proc and following all the tutorials
> online on how to modify it, this hackery is not sane.
>
It's not that bad:
(using the old acpidmp. I expect it works the same with acpidump, but
I couldn't get any output with my short tries ...)
acpidmp > /tmp/acpidmp
acpixtract dsdt /tmp/acpidmp >/tmp/dsdt
acpixtract ssdt /tmp/acpidmp >/tmp/ssdt
iasl -d /tmp/dsdt
if you have a ssdt:
iasl -d /tmp/ssdt
Now you can edit /tmp/ssdt.dsl and /tmp/dsdt.dsl
Thomas
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-07-27 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 17:24 acpidump replaces acpidmp Voluspa
[not found] ` <20050726192423.216b4be8.voluspa-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org>
2005-07-27 11:05 ` Thomas Renninger
[not found] ` <42E76A79.2040702-l3A5Bk7waGM@public.gmane.org>
2005-07-27 12:56 ` Voluspa
2005-07-27 13:44 ` Voluspa
[not found] ` <20050727154458.455d16db.voluspa-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org>
2005-07-27 15:05 ` Thomas Renninger [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-27 15:00 Brown, Len
2005-07-27 15:31 Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B300428C441-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-07-29 12:37 ` Thomas Renninger
2005-08-16 18:23 Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B300456A26A-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-08-16 21:32 ` Bjorn Helgaas
[not found] ` <200508161532.34578.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-17 7:45 ` Voluspa
2005-08-24 5:44 ` Len Brown
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=42E7A2A5.3040103@suse.de \
--to=trenn-l3a5bk7wagm@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=voluspa-zq6IREYz3ykAvxtiuMwx3w@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.