[OLPC-devel] Re: Why ACPI DSDT tables? ?JUNK MAIL? 4

Jordan Crouse jordan.crouse at amd.com
Mon Jul 10 16:45:12 EDT 2006


On 10/07/06 22:25 +0200, Stefan Reinauer wrote:
> So before we talk in big words of ACPI or no ACPI, what parts do we
> need from userspace:
>  * cpu powerstates
>  * display powerstates
>  * other parts of the system that can be powered down?
>  * poweroff, reboot, halt

Jim has already stated that power management from ACPI is off the table.
We can reliably ignore all of these. 

>  * what else? (and don't just write "ec")

We don't need ACPI to help us set up the interrupts.  We have no devices
that can only be set up through ACPI (such as an APIC).  We can get 
temp info through SMBus (if there is even a sensor on board - I don't know
if there is or not).  Regardless, we certainly don't want ACPI hijacking 
the SMBus because the DCON is attached to it.

So the only thing ACPI could possibly provide us is:

* Battery status 
* Button and lid events

Like I said before, I don't think thats worth bringing the interpreter along
for.

Jordan

-- 
Jordan Crouse
Senior Linux Engineer
Advanced Micro Devices, Inc.
<www.amd.com/embeddedprocessors>





More information about the Devel mailing list