Date: Fri, 12 Jun 2009 14:35:52 -0700 From: Nate Lawson <nate@root.org> To: Eygene Ryabinkin <rea-fbsd@codelabs.ru> Cc: freebsd-acpi@freebsd.org Subject: Re: [PATCH] acpidump: teach to disassemble arbitrary memory locations as AML code Message-ID: <4A32CA38.4020806@root.org> In-Reply-To: <W6QSpRPwDx1bM%2BckKMKVCUsLU5A@XX1fo6zQUfC4h0jjRC6IBz3oNH4> References: <W6QSpRPwDx1bM%2BckKMKVCUsLU5A@XX1fo6zQUfC4h0jjRC6IBz3oNH4>
next in thread | previous in thread | raw e-mail | index | archive | help
Eygene Ryabinkin wrote: > It is not uncommon when some chunks of the AML code are loaded by DSDT > from the memory locations that aren't part of the DSDT itself, but one > wants to see what's inside. It can be achieved with 'dd' and 'iasl', > but it is better to implement this machinery inside acpidump to ease the > life of both users and develepers that needs to see the full picture > of the ACPI stuff from foreign machines. > > This commit also have some small fixes: > > - verbose output (going to stderr) isn't mixed with normal output > that goes to stdout -- the latter is made unbuffered; > > - we're using IASL's logics to get the name of the output file and, > moreover, we prevent two simultaneous invocations of acpidump > to hose other's output; > > - IASL exit code is checked and if disassembler exited abnormally > or was failed to do its job, the warning is produced to give > the reader an idea on what's going on. > > Signed-off-by: Eygene Ryabinkin <rea-fbsd@codelabs.ru> 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. Any functions we need that it doesn't yet have can be submitted to Intel to merge. Thanks, -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A32CA38.4020806>