Re: ACPI request/release generic address

[Corey Minyard <minyard@acm.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Grover, Andrew wrote:

|>From: Jeff Garzik [mailto:jgarzik@pobox.com]
|>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.
|
|
|The Generic Address Structure (GAS) is basically a 64 bit address and a
|type field. The type can be:
|
|System memory
|System IO
|PCI Config space
|Embedded Controller
|SMBus
|Functional fixed hardware
|
|I don't think this will very easily handle a clean request/release API.
|Corey, what is the specific table you are concerned with? At least with
|the GASes ACPI uses internally, they point to resource regions already
|marked as used via other means (e820 or _CRS, for example.)

This is for some IPMI (Intelligent Platform Management Interface) hardware.
It's address is specified in an ACPI table.

- -Corey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+X8sDIXnXXONXERcRAraPAKCnPI1C7hfugkYVl0EOskoW2Tg61QCdHcfA
YnQrVlzYyYJssPU58cY4NU0=
=0Fqf
-----END PGP SIGNATURE-----