WDTT

[Moore, Robert]

What would be most helpful for us over here in ACPICA land is if your acpidump worked exactly like the Linux version. That is the most useful for debugging, and if you look at the linux bugzilla entries, you'll see that it is usually the very first thing we ask for when there is a problem.

The acpixtract utility is now provided with the ACPICA source, it is used to pull the binary tables from the acpidump.

I would like to make an ACPICA version of acpidump that is OS-independent so that there isn't a duplication of tools.



>-----Original Message-----
>From: owner-freebsd-acpi at freebsd.org [mailto:owner-freebsd-
>acpi at freebsd.org] On Behalf Of Nate Lawson
>Sent: Wednesday, January 14, 2009 9:32 AM
>To: Andriy Gapon
>Cc: freebsd-acpi at freebsd.org
>Subject: Re: WDTT
>
>Andriy Gapon wrote:
>> on 14/01/2009 19:06 Nate Lawson said the following:
>>> You need both the -t and -d flags. See the man page. Maybe that should
>>> be made the default, although I didn't like the idea of a command
>>> dumping out pages of output when run with no flags.
>>
>> Nate,
>>
>> This doesn't work for me, at least on stable/7.
>> The tables are not "dumped", they are "pretty-printed", but that happens
>> only for a subset of tables - for unknown tables just a standard header
>> is printed, the actual data is not.
>>
>> And it seems that while there is a way to dump "raw" DSDT, there is no
>> way to dump other tables in a raw form.
>
>I see. Yeah, perhaps you could add a patch that does a hex dump of
>unknown tables or a way to specify a table id and get the raw binary
>data. Perhaps -i id would be good.
>
>Example:
>    acpidump -t
>See that WDTT is interesting.
>    acpidump -i WDTT -o wdtt.bin
>
>What do you think?
>
>--
>Nate
>_______________________________________________
>freebsd-acpi at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
>To unsubscribe, send any mail to "freebsd-acpi-unsubscribe at freebsd.org"