Skip to contentSkip to conversation

ACPI 2.0 support

Linux-ia64 Alex Williamson 3 participants 4 messages Nov 17, 2000 – Nov 20, 2000

lore
Share & tools
lore
#0 lore raw

I've been working on adding ACPI 2.0 table support for IA-64 in
preparation for McKinley systems. I have a preliminary version that correctly parses 2.0 tables on an architectural simulator. I'd also like to get Intel's drop of the ACPI CA w/ 2.0 support added into the kernel as quickly as possible. Is there a current maintainer of IA-64 ACPI support? Is there anyone else interested in working on this or testing it?

I'd also like to incorporate using ACPI methods to get resource
information for programming PCI devices, eventually leading to support for hot-plug PCI via ACPI. Anyone have any thoughts or interest there? Thanks,

Alex

--
Alex Williamson Linux Development Lab
[email protected] Hewlett Packard
970-898-9173 Fort Collins, CO

#1 lore raw

Intel has done the ACPI 2.0 table parsing and testing with FWs that support ACPI 2.0 tables. We are planning to integrate this code in the next release. These works are done primarily in preparation for McKinley systems.

Thanks,
Asit

Quoted 33 lines

-----Original Message-----
From: Alex Williamson [mailto:[email protected]]
Sent: Friday, November 17, 2000 12:12 PM
To: [email protected]
Subject: [Linux-ia64] ACPI 2.0 support

I've been working on adding ACPI 2.0 table support for IA-64 in
preparation for McKinley systems. I have a preliminary version that correctly parses 2.0 tables on an architectural simulator. I'd also like to get Intel's drop of the ACPI CA w/ 2.0 support added into the kernel as quickly as possible. Is there a current maintainer of IA-64 ACPI support? Is there anyone else interested in working on this or testing it?

I'd also like to incorporate using ACPI methods to get resource
information for programming PCI devices, eventually leading to support for hot-plug PCI via ACPI. Anyone have any thoughts or interest there? Thanks,

Alex

--
Alex Williamson Linux Development Lab
[email protected] Hewlett Packard
970-898-9173 Fort Collins, CO

_______________________________________________
Linux-IA64 mailing list
[email protected]
http://lists.linuxia64.org/lists/listinfo/linux-ia64

#2 lore raw
In reply to Alex Williamson
Quoted 4 lines

I'd also like to incorporate using ACPI methods to get resource
information for programming PCI devices, eventually leading to support for hot-plug PCI via ACPI. Anyone have any thoughts or interest there? Thanks,

I hope folks don't mind a stranger dropping in on this discussion; I've been doing similar work for the IA32 and IA64 FreeBSD codebase though and this is a point I've been looking at for a while.

The key item to bear in mind here is that ACPI stays out of the way of other enumeration mechanisms; meaning that ACPI itself isn't going to help you very much when it comes to resource information for newly-arrived PCI devices, other than routing interrupts for them (and even then your bridge driver will still have to correctly swizzle for devices on the other side of the bridge).

I've written (but not verified) code that uses the Intel ACPI CA codebase to route PCI interrupts for the host-PCI bridge; I'd be happy to furnish this on request, although in truth the documentation is enough to make this a largely trivial task.

As for allocating memory ranges and configuring intermediate bridges; ACPI doesn't play a role here at all (so far as I've seen, at any rate).

Hope this helps.

Mike

Signature · 5 lines
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E
#3 lore raw
In reply to Alex Williamson
Quoted 17 lines · Mike Smith
Quoted 5 lines

I'd also like to incorporate using ACPI methods to get resource
information for programming PCI devices, eventually leading to support for hot-plug PCI via ACPI. Anyone have any thoughts or interest there? Thanks,

I hope folks don't mind a stranger dropping in on this discussion; I've been doing similar work for the IA32 and IA64 FreeBSD codebase though and this is a point I've been looking at for a while.

The key item to bear in mind here is that ACPI stays out of the way of other enumeration mechanisms; meaning that ACPI itself isn't going to help you very much when it comes to resource information for newly-arrived PCI devices, other than routing interrupts for them (and even then your bridge driver will still have to correctly swizzle for devices on the other side of the bridge).

Quoted 8 lines

I've written (but not verified) code that uses the Intel ACPI CA codebase to route PCI interrupts for the host-PCI bridge; I'd be happy to furnish this on request, although in truth the documentation is enough to make this a largely trivial task.

As for allocating memory ranges and configuring intermediate bridges; ACPI doesn't play a role here at all (so far as I've seen, at any rate).

Not yet ;) They key thing to remember here is that the resources
available to a PCI bus are typically static, even if PCI devices can be inserted and removed. So, the _CRS/_PRS methods should be able to provide the necessary resource information for newly inserted PCI devices. This will, of course, be dependent on the ACPI firmware vendor doing a sufficient implementation and the system providing sufficient MMIO/IO port space for added devices on each PCI bus. If ACPI won't work for us in determining valid PCI resources, then what chipset independent mechanism do we have? As we move to systems designed with more high availability features, I see firmware playing less of a role in actually programming the resource registers on PCI devices. Firmware will likely lean more towards providing mechanisms by which the OS can do it on it's own.

Alex

--
Alex Williamson Linux Development Lab
[email protected] Hewlett Packard
970-898-9173 Fort Collins, CO