WDTT

[Moore, Robert]

>Then I'd prefer we just keep our nice parsing for tables we know of and

I think that even this may be obsolete. iASL -d will now disassemble all known ACPI tables, including both tables that contain AML and those that contain only data.

For example,

/*
 * Intel ACPI Component Architecture
 * AML Disassembler version 20081204
 *
 * Disassembly of MCFG.dat, Wed Jan 14 10:32:45 2009
 *
 * ACPI Data Table [MCFG]
 *
 * Format: [HexOffset DecimalOffset ByteLength]  FieldName : FieldValue
 */

[000h 000  4]                    Signature : "MCFG"    /* Memory Mapped Configuration table */
[004h 004  4]                 Table Length : 0000003C
[008h 008  1]                     Revision : 01
[009h 009  1]                     Checksum : 84
[00Ah 010  6]                       Oem ID : "HP    "
[010h 016  8]                 Oem Table ID : "0944    "
[018h 024  4]                 Oem Revision : 00000001
[01Ch 028  4]              Asl Compiler ID : "HP  "
[020h 032  4]        Asl Compiler Revision : 00000001

[024h 036  8]                     Reserved : 0000000000000000

[02Ch 044  8]                 Base Address : 00000000E0000000
[034h 052  2]         Segment Group Number : 0000
[036h 054  1]             Start Bus Number : 00
[037h 055  1]               End Bus Number : FF
[038h 056  4]                     Reserved : 00000000

Raw Table Data

  0000: 4D 43 46 47 3C 00 00 00 01 84 48 50 20 20 20 20  MCFG<.....HP    
  0010: 30 39 34 34 20 20 20 20 01 00 00 00 48 50 20 20  0944    ....HP  
  0020: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 E0  ................
  0030: 00 00 00 00 00 00 00 FF 00 00 00 00              ............


>-----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 10:19 AM
>To: Andriy Gapon
>Cc: freebsd-acpi at freebsd.org; Moore, Robert
>Subject: Re: WDTT
>
>Andriy Gapon wrote:
>> on 14/01/2009 19:45 Nate Lawson said the following:
>>> Last time I looked, the Linux one did no parsing of extended tables,
>>> just dumped binary data. It only parsed ASL. This was not very useful
>>> since our PRs are mostly email based, and decoding a binary attachment
>>> just to find the SCI irq settings in the MADT was untenable.
>>>
>>> Has that changed?
>>
>> Yes, it looks like binary data piped through hd/hexdump with small
>> headings for each table.
>>
>>> Moore, Robert wrote:
>>>> 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.
>
>Then I'd prefer we just keep our nice parsing for tables we know of and
>print a hexdump by default for tables we don't. Seems simple and
>compatible enough.
>
>Care to provide a patch?
>
>--
>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"