Hi,
> On Mon, Oct 01, 2001 at 10:50:17AM +0200, Georg-W. Koltermann wrote:
> > Hi,
> >
> > I'm wondering how I should handle APM now that ACPI has basically
> > taken over power management responsibility.
>
> APM and ACPI are mutually exclusive from what I understand. You should
> remove the apm device from your kernel config.
Yes, some older machines w/ ACPI can support both of them at the same time,
but most modern machines don't.
> > It seems I still need to configure APM so that /dev/apm is there and
> > battery monitoring utilities like the GNOME battery_applet can work.
>
> Battery, temp, etc, can be monitored via the hw.acpi sysctl tree.
> Someone will have to do the required conversion to the various APM
> utilities is GNOME and whatever else.
Yes, you can get battery info. in C code like;
sysctlbyname("hw.acpi.battery.time", &percent, &len, NULL, 0);
Note that these MIBs maybe change in future...
Generalized power-management interface API to have compatibility with
APM and ACPI also is suggested long time ago;
http://www.freebsd.org/cgi/getmsg.cgi?fetch=403390+406841+/usr/local/www/db/text/2001/freebsd-current/20010114.freebsd-current
Device node for ACPI is discussed bofore too; having only one /dev/acpi
or having generalized nodes for each device types such as /dev/battery0
but we couldn't reach the conclusion, now discussion stops...
Any suggestions on it? Once we get the conclusion, we can start developing
API and convert userland tools.
> > I also was able to suspend and resume my machine (DELL Inspiron 7500)
> > with APM being configured (and ACPI being active by default). Sound
> > is dead after a resume,
>
> What sound card?
>
> > PCMCIA is dead after a couple of resumes,
>
> Resource leak? Warner?
Is yours similar to any data at there (Dell_I7500*) ?
http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp
I guess CardBus controllers are _SB_.PCI0.CB1_ and _SB_.PCI0.CB2_
but I didn't see any sleep/wakeup hack for them...
Thanks
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
