> > **resource management**
> > Non-ACPI platforms uses $HRT/EBDA, pcibios_*(), SMBIOS,
> etc. for slot
> > enumeration/configuration.
> > DIG64/ACPI, and SHPC requires ACPI for this. IPF platforms
> only have ACPI
> > _CRS, _PRT, _HPP, _BBN, _STA, _ADR, _SUN, etc on the
> namespace for PHP, and
> > we have to use them. (as a side note, this functionality is
> common for other
> > hotplug-* as mentioned in first mail. No API will be common for
> > hotplug-everything, but functionality is common and has not to be
> > duplicated)
>
> > **event management in terms of controller/slot operations **
> > ACPI provides only _EJ0, _PS?, _STA, etc for slot
> operations but these are
> > not mandatory. That means, we can use either ACPI method or
> controller
> > driver.
> > intcphp driver has not enabled ACPI method based solution but uses
> > controller driver.
> > intcphp driver is also capable of performing ACPI method
> based solution
> > since it works on ACPI namespace. This is why acpiphp and
> intcphp could be
> > sharing resource management and event management.
>
> Sounds like we want a library of ACPI code that can be used
> by individual
> drivers rather than an ACPI driver with pluggable event management
> functions then.
Right, that's where we're getting at.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Oct 31 2002 - 22:00:24 EST