Home | History | Annotate | Line # | Download | only in acpi
TODO revision 1.13 
      1   1.1  mycroft Important things to make ACPI useful on more machines:
      2   1.1  mycroft 
      3  1.11   sekiya * Fix problems with PCI_INTR_FIXUP.  The current code always chooses the last
      4  1.11   sekiya   possible interrupt, which causes problems when that interrupt is shared with
      5  1.11   sekiya   an ISA device.  http://mail-index.netbsd.org/tech-kern/2005/11/11/0011.html
      6  1.11   sekiya   has a more detailed analysis.
      7   1.3  mycroft 
      8  1.11   sekiya - sekiya, 21 December 2005
      9  1.13   jruoho 
     10  1.13   jruoho * The mismatch between the conventional and the ACPI device tree is the single
     11  1.13   jruoho   biggest architectural problem in the current stack. Various power management
     12  1.13   jruoho   features rely on the interaction between the firmware (ACPI) and the native
     13  1.13   jruoho   drivers. Examples include, but are not limited to, WoL, PCI power management,
     14  1.13   jruoho   and runtime power management (which involves GPEs on the ACPI side).
     15  1.13   jruoho 
     16  1.13   jruoho   Devices should not attach to acpi(4), but should still use ACPI to reserve
     17  1.13   jruoho   PCI, ISA, and other resources. This includes also buses such as I2C where
     18  1.13   jruoho   resource conflicts and other bus errors are widely known to exist.
     19  1.13   jruoho 
     20  1.13   jruoho   A satisfactory solution involves full or partial redesign of the x86
     21  1.13   jruoho   autoconfiguration process. The current ad-hoc solutions used for instance
     22  1.13   jruoho   in acpi_pci.c are inefficient and ugly.
     23  1.13   jruoho 
     24  1.13   jruoho * Related to previous, investigate how existing systems can interact with
     25  1.13   jruoho   the BIOS and ACPI. For instance, at the moment of writing this, IPMI is
     26  1.13   jruoho   already available via ACPI. In the future this may cause possible conflicts
     27  1.13   jruoho   between ipmi(4) and the firmware.
     28  1.13   jruoho 
     29  1.13   jruoho * Not directly related to ACPI, but implement S4 a.k.a. suspend-to-disk.
     30  1.13   jruoho 
     31  1.13   jruoho * Improve IA-64 ACPI support. Even if the architecture may be rare,
     32  1.13   jruoho   support for Itanium is a good way to ensure that the stack remains MI.
     33  1.13   jruoho 
     34  1.13   jruoho * Implement the ACPI requirements for CPU hot-plug.
     35  1.13   jruoho 
     36  1.13   jruoho * Support APEI (ACPI Platform Error Interface).
     37  1.13   jruoho 
     38  1.13   jruoho * Support ACPI 4.0 devices.
     39  1.13   jruoho 
     40  1.13   jruoho - jruoho, 23 June 2011
     41