[PATCH] acpidump: teach to disassemble arbitrary memory locations as AML code

[Moore, Robert]

I should point out that acpidump was never "linuxed", it was simply written as native Linux code.


>-----Original Message-----
>From: owner-freebsd-acpi at freebsd.org [mailto:owner-freebsd-
>acpi at freebsd.org] On Behalf Of Moore, Robert
>Sent: Wednesday, June 17, 2009 10:06 AM
>To: rea-fbsd at codelabs.ru; Nate Lawson; Jung-uk Kim
>Cc: freebsd-acpi at freebsd.org
>Subject: RE: [PATCH] acpidump: teach to disassemble arbitrary memory
>locations as AML code
>
>The raw ACPICA source code is run through a converter (acpisrc) to
>"linuxize" the code before it is integrated into Linux.
>
>
>>-----Original Message-----
>>From: rea-fbsd at codelabs.ru [mailto:rea-fbsd at codelabs.ru]
>>Sent: Tuesday, June 16, 2009 11:11 PM
>>To: Nate Lawson; Jung-uk Kim
>>Cc: freebsd-acpi at freebsd.org; Moore, Robert
>>Subject: Re: [PATCH] acpidump: teach to disassemble arbitrary memory
>>locations as AML code
>>
>>Nate, Jung-uk, good day.
>>
>>Fri, Jun 12, 2009 at 02:35:52PM -0700, Nate Lawson wrote:
>>> I appreciate your work. What we need to do though is remove acpidump(8)
>>> from the system and import Intel's acpidmp utility. It's included in the
>>> ACPI-CA distribution and is functional enough that we can use it.
>>
>>OK, I'll try to take a look at it.  But this is a future work;
>>meanwhile, can we still extend acpidump in a way I propose.  I have the
>>updated patch that applies on top of the -CURRENT tree after the recent
>>ACPICA import, but I have some troubles with 'make depend' inside
>>usr.sbin/acpi/acpidb, so once I'll resolve them and test the stuff with
>>full buildworld -- I'll post the patch as an update.
>>
>>Fri, Jun 12, 2009 at 06:34:27PM -0400, Jung-uk Kim wrote:
>>> On Friday 12 June 2009 06:02 pm, Moore, Robert wrote:
>>> > Actually, we don't distribute an acpidump (yet) in ACPICA. The
>>> > Linux version is part of the "pmtools" package.
>>> >
>>> > It is of course, linux-specific. I won't distribute it with ACPICA
>>> > until we have an OS-independent version. It is on our list of
>>> > things to-do.
>>>
>>> FYI, it won't be terribly hard to port it because we also use
>>> /dev/mem.  However, the source is acpisrc'ified and we cannot undo it
>>> to make it compile on FreeBSD. :-(
>>
>>Haven't looked at the source yet, so probably the question is very dumb,
>>but nevertheless: what do you mean by "acpisrc'ified"?
>>
>>And a general question: is there a VCS repository for the pmtools, or at
>>least the download location with snapshots/releases?  My Google-fu fails
>>on this and moblin.org doesn't seem to have this stuff available.
>>
>>Thanks!
>>--
>>Eygene
>> _                ___       _.--.   #
>> \`.|\..----...-'`   `-._.-'_.-'`   #  Remember that it is hard
>> /  ' `         ,       __.--'      #  to read the on-line manual
>> )/' _/     \   `-_,   /            #  while single-stepping the kernel.
>> `-'" `"\_  ,_.-;_.-\_ ',  fsc/as   #
>>     _.-'_./   {_.'   ; /           #    -- FreeBSD Developers handbook
>>    {_.-``-'         {_/            #
>_______________________________________________
>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"