Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Jan 2009 10:19:07 -0800
From:      Nate Lawson <nate@root.org>
To:        Andriy Gapon <avg@icyb.net.ua>
Cc:        "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org>, "Moore, Robert" <robert.moore@intel.com>
Subject:   Re: WDTT
Message-ID:  <496E2C9B.3000907@root.org>
In-Reply-To: <496E25AB.8050900@icyb.net.ua>
References:  <4968B843.8020108@icyb.net.ua>	<4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com>	<496DB197.5020100@icyb.net.ua>	<4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com>	<496E0F90.3000507@icyb.net.ua>	<4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com>	<496E1B90.8080406@root.org> <496E1DE0.5080305@icyb.net.ua> <496E2192.5030906@root.org> <4911F71203A09E4D9981D27F9D8308580E4EAB6A@orsmsx503.amr.corp.intel.com> <496E24BF.50206@root.org> <496E25AB.8050900@icyb.net.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?496E2C9B.3000907>