public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Takayoshi Kochi <t-kochi-UDFczIW9X1d8UrSeD/g0lQ@public.gmane.org>
Subject: Re: Re: DSDT > 128k support
Date: Wed, 17 Nov 2004 12:23:12 -0700	[thread overview]
Message-ID: <200411171223.12417.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <1100713897.993.8.camel@d845pe>

On Wednesday 17 November 2004 10:51 am, Len Brown wrote:
> I think the code in the kernel to supply /proc/acpi/dsdt
> and /proc/acpi/fadt should be deleted.  This capability
> and more can be had entirely from a user-space /dev/mem reader
> such as acpidmp in the pmtools package:
> 
> http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/

Except that acpidmp still gropes through 0x000e0000-0x00100000
looking for something that looks like an RSDP.  I don't think
that works on ia64.  (We do provide /sys/firmware/efi/systab,
which contains the address you need, so acpidmp could probably
use that when it's available.)


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

  reply	other threads:[~2004-11-17 19:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17 14:08 DSDT > 128k support Takayoshi Kochi
     [not found] ` <20041117.230831.74752627.t-kochi-UDFczIW9X1d8UrSeD/g0lQ@public.gmane.org>
2004-11-17 14:11   ` Takayoshi Kochi
2004-11-17 17:51   ` Len Brown
2004-11-17 19:23     ` Bjorn Helgaas [this message]
     [not found]       ` <200411171223.12417.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2004-11-18  6:24         ` Takayoshi Kochi

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=200411171223.12417.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=t-kochi-UDFczIW9X1d8UrSeD/g0lQ@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