path: root/ObsoleteFiles.inc
diff options
authorNate Lawson <njl@FreeBSD.org>2005-07-23 19:36:00 +0000
committerNate Lawson <njl@FreeBSD.org>2005-07-23 19:36:00 +0000
commit76f6fe4f31fa9c97f4a6f7713149ed9950323286 (patch)
tree098bd44131b4884e3f9bfa4b18f7728aa68f1ff4 /ObsoleteFiles.inc
parentd3a46d12534fcaf88c90cc8eb2a2e75f10e2c457 (diff)
Rewrite the acpi_battery interface to allow for other battery types
(i.e., smart battery) and fix various bugs found during the cleanup. API changes: * kernel access: Access to individual batteries is now via devclass_find("battery"). Introduce new methods ACPI_BATT_GET_STATUS (for _BST-formatted data) and ACPI_BATT_GET_INFO (for _BIF-formatted data). The helper function acpi_battery_get_battinfo() now takes a device_t instead of a unit # argument. If dev is NULL, this signifies all batteries. * ioctl access: The ACPIIO_BATT_GET_TYPE and ACPIIO_BATT_GET_BATTDESC ioctls have been removed. Since there is now no need for a mapping between "virtual" unit and physical unit, usermode programs can just specify the unit directly and skip the old translation steps. In fact, acpiconf(8) was actually already doing this and virtual unit was the same as physical unit in all cases since there was previously only one battery type (acpi_cmbat). Additionally, we now map the ACPIIO_BATT_GET_BIF and ACPIIO_BATT_GET_BST ioctls for all batteries, if they provide the associated methods. * apm compatibility device/ioctls: no change * sysctl: no change Since most third-party applications use the apm(4) compat interface, there should be very few affected applications (if any). Reviewed by: bruno MFC after: 5 days
Notes: svn path=/head/; revision=148352
Diffstat (limited to 'ObsoleteFiles.inc')
0 files changed, 0 insertions, 0 deletions