The main reason I supported Acpi phase I was to get started with multi-core.

Yet a more complete mobile system is important too. I would contribute to this bounty, even though it may not be a high priority.

I wonder, how much effort it would take to get this done?

With ACPI (Phase I) complete thanks to Pavel, I think it would be good to get the Phase II bounty bubbling away.

Here's a rough spec in layman's terms. I've concentrated on battery/power management features, leaving device support like PCI Express for a separate bounty (thoughts?)

I'd be grateful if a developer could add any technical specifics, such as implementation detail and how functionality should be exposed to applications. Feel free to scrap my text entirely if you wish... I won't be offended!

Requirements

* Implement 'Sleep' mode

[According to the Idiot's Guide To ACPI AKA Wikipedia, I presume the correct ACPI State is G1 (S3)]

Demonstrated with a CLI command and/or Wanderer menu-item.

* Battery management/monitoring

Demonstrate with a small application showing battery information - whether machine is running off battery or mains power, percentage of battery charge, time remaining and time to full charge.

AROS alerts the user when battery is low. AROS is put to sleep when battery reaches a critical level.

* Implement Hibernate/Suspend to disk (optional?)

[State G1 (S4)?]

Demonstrated with a CLI command and/or Wanderer menu-item.

Chris