public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Cc: "Starikovskiy,
	Alexey Y"
	<alexey.y.starikovskiy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Voluspa <voluspa-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org>
Subject: Re: RE: acpidump replaces acpidmp
Date: Wed, 24 Aug 2005 01:44:12 -0400	[thread overview]
Message-ID: <1124862252.28987.5.camel@firebird.lenb.worldpath.net> (raw)
In-Reply-To: <200508161532.34578.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>

On Tue, 2005-08-16 at 17:32 -0400, Bjorn Helgaas wrote:
> On Tuesday 16 August 2005 12:23 pm, Brown, Len wrote:
> > Mats,
> > Does the latest acpidump work for you now?
> > can we obsolete /proc/acpi/fadt,dsdt?
> 
> pmtools-20050804 doesn't work at all on ia64, because
> the RSDP doesn't live where you expect it.  We export
> /sys/firmware/efi/systab with the addresses you want.
> 
> The attached patch adds this, fixes a bunch of
> documentation errors, and fixes some broken if/else
> blocking.  There are still a number of warnings when
> building on ia64; I didn't bother to fix those, sorry.

Thanks Bjorn.
Alexey included your patch in pmtools-20050823,
and has now tested the latest on IA64 systems with
and without /sys/firmware/efi.

http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20050823.tar.gz

cheers,
-Len




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  parent reply	other threads:[~2005-08-24  5:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 18:23 acpidump replaces acpidmp Brown, Len
     [not found] ` <F7DC2337C7631D4386A2DF6E8FB22B300456A26A-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-08-16 21:32   ` Bjorn Helgaas
     [not found]     ` <200508161532.34578.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-17  7:45       ` Voluspa
2005-08-24  5:44       ` Len Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-27 15:31 Brown, Len
     [not found] ` <F7DC2337C7631D4386A2DF6E8FB22B300428C441-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-07-29 12:37   ` Thomas Renninger
2005-07-27 15:00 Brown, Len
2005-07-26 17:24 Voluspa
     [not found] ` <20050726192423.216b4be8.voluspa-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org>
2005-07-27 11:05   ` Thomas Renninger
     [not found]     ` <42E76A79.2040702-l3A5Bk7waGM@public.gmane.org>
2005-07-27 12:56       ` Voluspa
2005-07-27 13:44       ` Voluspa
     [not found]         ` <20050727154458.455d16db.voluspa-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org>
2005-07-27 15:05           ` Thomas Renninger

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=1124862252.28987.5.camel@firebird.lenb.worldpath.net \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=alexey.y.starikovskiy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=bjorn.helgaas-VXdhtT5mjnY@public.gmane.org \
    --cc=voluspa-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org \
    /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