public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot@poupinou.org>
To: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
Cc: trenn@suse.de, "Moore, Robert" <robert.moore@intel.com>,
	"Brown, Len" <len.brown@intel.com>,
	linux-acpi@vger.kernel.org
Subject: Re: new pmtools available for testing
Date: Wed, 29 Nov 2006 17:31:09 +0100	[thread overview]
Message-ID: <20061129163109.GN4945@poupinou.org> (raw)
In-Reply-To: <456C410D.9090201@linux.intel.com>

On Tue, Nov 28, 2006 at 05:00:45PM +0300, Alexey Starikovskiy wrote:
> Writing new utility from scratch took half a day, while porting ACPICA 
> acpidump with change in license would take weeks.
> It does include ACPICA types, so it will require ACPICA headers at least.
> Also it relies on ACPICA subset of libc, so it will be pain to both 
> maintain it  and  make any improvements.
> We already tried to have acpidump utility in both ACPICA and pmtools and 
> ended with two completely different programs.
> 

I don't get it.

ducrot@neptune:~/packages$ cp -r acpica-unix-20060912/tools/acpixtract/ .
ducrot@neptune:~/packages$ cd acpixtract/
ducrot@neptune:~/packages/acpixtract$ make
cc -Wall -O2 -D_LINUX -DACPI_APPLICATION -Wstrict-prototypes -I../../include    -c -o acpixtract.o acpixtract.c
cc  acpixtract.o -o acpixtract
ducrot@neptune:~/packages/acpixtract$ 

How acpixtract need ACPICA specific headers?

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

  reply	other threads:[~2006-11-29 16:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27 18:13 new pmtools available for testing 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-12 22:35 Moore, Robert
2006-11-21 18:24 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

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=20061129163109.GN4945@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=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