You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Devices with scope != System should be ignored, since it is impossible to expect from drivers to provide the same amount of information as in case of system batteries.
- Public methods and internal calculations are now using uom types only.
- Rename `Battery::percentage` method into `Battery::state_of_charge`
- Rename `Battery::capacity` method into `Battery::state_of_health`
- Mark `battery::State` and `battery::Technology` enums as a non-exhaustive
- Ignore devices with `scope` attributes different from `System` for Linux [#18](#18)
Both battery and battery-ffi are now propagating possible errors to callers.
Supporting multiple devices for FreeBSD and DragonFlyBSD systems (closes#17)
Ignoring Linux devices with scope other than System (closes#18).
Both battery and battery-ffi are now propagating possible errors to callers.
Supporting multiple devices for FreeBSD and DragonFlyBSD systems (closes#17)
Ignoring Linux devices with scope other than System (closes#18).
Devices with
scope != System
should be ignored, since it is impossible to expect from drivers to provide the same amount of information as in case of system batteries.scope
attribute was introduced in this patch: http://lkml.iu.edu/hypermail/linux/kernel/1112.0/03454.htmlExample of the battery report from the connected mice, reported by @o10g:
The text was updated successfully, but these errors were encountered: