public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>,
	robert.moore@intel.com
Cc: Mattia Dongili <malattia@linux.it>, linux-acpi@vger.kernel.org
Subject: Re: new pmtools available for testing
Date: Mon, 11 Dec 2006 13:20:18 -0500	[thread overview]
Message-ID: <200612111320.19183.lenb@kernel.org> (raw)
In-Reply-To: <457C3FC4.8070804@linux.intel.com>

Bob,
Any chance you could tweak the C acpixtract so it can handle
the parameter format of the old perl script?

I like the newer way better, but it looks like  backwards compatibility
is within our grasp without mucking it up, so I think we should do it.

On Sunday 10 December 2006 12:11, Alexey Starikovskiy wrote:
> Mattia Dongili wrote:
> > On Tue, Nov 21, 2006 at 09:24:25PM +0300, Alexey Starikovskiy wrote:
> >   
> >> Hi,
> >>
> >> acpixtract perl-script is being replaced by C xtract utility. Please test.
> >>     
> >
> > Hello, I'm considering an update to the acpidump Debian package, so is
> > this version (20061121) available online somewhere?
> > Should it just appear in Len's kernel.org FTP when it's ready?
> >
> > Thanks
> >   
> Len is about to put 20061130 version out, with acpixtract from ACPI CA 
> package.

Well, I pushed this up to the ftp site, and it is functional, but the problem
is that the new acpixtract from ACPICA has different parameters, so it
isn't backwards compatible with the old per acpixtract.

the examples in pmtools/README include invocations like this:
    $ cat email | ./acpixtract DSDT > DSDT
    $ cat email | ./acpixtract FACP | ./acpitbl
    $ ./acpixtract FACP acpidump.out > FACP.bin
    $ ./acpixtract -n 3 SSDT acpidump.out > SSDT3.bin

but the new acpixtract looks like this:

# ./acpixtract FACP acpidump.out > FACP.bin
# cat FACP.bin
Could not open FACP
#
# ./acpixtract -n 3 SSDT acpidump.out > SSDT3.bin
# cat SSDT3.bin
Usage: acpixtract [option] <InputFile>

Extract binary ACPI tables from text acpidump output
Default invocation extracts all DSDTs and SSDTs
Version 20060324

Options:
 -a                    Extract all tables, not just DSDT/SSDT
 -l                    List table summaries, do not extract
 -s<Signature>         Extract all tables named <Signature>


  reply	other threads:[~2006-12-11 18:17 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
2006-12-10 15:50 ` Mattia Dongili
2006-12-10 17:11   ` Alexey Starikovskiy
2006-12-11 18:20     ` Len Brown [this message]
  -- 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=200612111320.19183.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=alexey.y.starikovskiy@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=malattia@linux.it \
    --cc=robert.moore@intel.com \
    /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