From: Corey Minyard <minyard@acm.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI request/release generic address
Date: Fri, 28 Feb 2003 12:22:36 -0600 [thread overview]
Message-ID: <3E5FA8EC.7030607@acm.org> (raw)
In-Reply-To: <20030228163253.GB6351@gtf.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It an acpi_generic_address structure defined in include/acpi/actbl2.h.
It's an address that can be in memory, I/O, or PCI configuration space.
The definition is at http://www.microsoft.com/hwdev/tech/onnow/LF-ACPI.asp
- -Corey
Jeff Garzik wrote:
|On Fri, Feb 28, 2003 at 10:26:13AM -0600, Corey Minyard wrote:
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>Is there a way in the ACPI code to do a request/release of I/O or memory
|>with an acpi_generic_address? Does it even make sense to do this?
|>There are generic I/O routines for using a generic address, and I'm
|>working with an ACPI table that has a generic address, so it would seem
|>to make sense to have memory reservation routines through this, too.
|
|
|Can you define a generic address?
|
|IIRC, ACPI needs some work in this area.
|
|If the "generic address" is host RAM, that's easy.
|If the generic address is PIO address, that's mostly easy.
|If the generic address is MMIO address, that takes a bit of care with
|mapping, and I'm not sure ACPI gets it right in these cases.
|
| Jeff
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE+X6jqIXnXXONXERcRAtghAKCpyo6enCR91Affkq9lwDRIRQleTwCeIC1t
TlYA0vFQIvYWCKf7IknAG90=
=BG4s
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-02-28 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 16:26 ACPI request/release generic address Corey Minyard
2003-02-28 16:32 ` Jeff Garzik
2003-02-28 18:22 ` Corey Minyard [this message]
2003-02-28 18:28 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-02-28 16:49 Grover, Andrew
2003-02-28 20:48 ` Corey Minyard
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=3E5FA8EC.7030607@acm.org \
--to=minyard@acm.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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