From: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
To: trenn@suse.de
Cc: "Brown, Len" <len.brown@intel.com>,
linux-acpi@vger.kernel.org, "Moore,
Robert" <robert.moore@intel.com>
Subject: Re: new pmtools available for testing
Date: Wed, 22 Nov 2006 19:40:36 +0300 [thread overview]
Message-ID: <45647D84.9020101@linux.intel.com> (raw)
In-Reply-To: <1164209126.3721.363.camel@queen.suse.de>
Thomas Renninger wrote:
> On Wed, 2006-11-22 at 17:36 +0300, Alexey Starikovskiy wrote:
>
>> Thomas Renninger wrote:
>>
>>> On Tue, 2006-11-21 at 21:24 +0300, Alexey Starikovskiy wrote:
>>>
>>>
>>>> Hi,
>>>>
>>>> acpixtract perl-script is being replaced by C xtract utility. Please test.
>>>> Advances are:
>>>> - Perl not required :)
>>>> - no 64k output limit of perl-script
>>>> - --list option shows all tables in the file
>>>> - unified interface with acpidump
>>>> - faster(?)
>>>>
>>>> Thanks in advance,
>>>>
>>>>
>>> Is this acpixtract that already existed in ACPICA since some time and
>>> now moved to pmtools?
>>>
>>>
>> Nope, it's duplicated effort.
>>
>
> Hmm, you should talk to (I think acpixtract C prog came from) Bob?
> Someone should decide which should be the final one everybody should
> use...
> If one distri or application starts to package and use the one, others
> start to use the other, we might have compatibility problems in some
> scripts in future.
>
>
New utility is names 'xtract' so it does not clash with 'acpixtract'
either perl-script or ACPICA utility.
If are used to acpixtract, no need to change your habits. If you somehow
tired of crippled interface, you could try new utility.
> The linuxfirmwarekit makes use of ACPICA's acpixtract AFAIK (hardcoded
> by something like system("acpixtract acpidump");).
> I also packaged this one into SUSE pmtools package (since SUSE 10.1?).
> -> I'd prefer to stick to the ACPICA's acpixtract..
>
no problem at all.
Regards,
Alex
next prev parent reply other threads:[~2006-11-22 16:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 18:24 new pmtools available for testing Alexey Starikovskiy
2006-11-21 18:27 ` Alexey Starikovskiy
2006-11-22 13:55 ` Thomas Renninger
2006-11-22 14:36 ` Alexey Starikovskiy
2006-11-22 15:25 ` Thomas Renninger
2006-11-22 16:40 ` Alexey Starikovskiy [this message]
2006-12-10 15:50 ` Mattia Dongili
2006-12-10 17:11 ` Alexey Starikovskiy
2006-12-11 18:20 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2006-11-27 18:13 Moore, Robert
2006-11-28 10:03 ` Thomas Renninger
2006-11-28 10:24 ` Alexey Starikovskiy
2006-11-28 11:14 ` Thomas Renninger
2006-11-28 14:00 ` Alexey Starikovskiy
2006-11-29 16:31 ` Bruno Ducrot
2006-12-12 22:35 Moore, Robert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45647D84.9020101@linux.intel.com \
--to=alexey.y.starikovskiy@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=trenn@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox