Displaying 3 results from an estimated 3 matches for "ac_adaptor".
Did you mean:
ac_adapter
2007 Jun 01
0
HAL and NUT feedback
...ed in some more info:
> > - lshal -u <your device's UDI>
> > the UDI can be obtained for ex. through hal-device-manager
>
> lshal -lu /org/freedesktop/Hal/devices/usb_device_592_2_noserial
> udi = '/org/freedesktop/Hal/devices/usb_device_592_2_noserial'
> ac_adaptor.present = true (bool)
> battery.charge_level.design = 100 (0x64) (int)
> battery.charge_level.last_full = 100 (0x64) (int)
> battery.charge_level.unit = 'percent' (string)
> battery.is_rechargeable = true (bool)
> battery.model = 'POWERWARE UPS 500VA...
2006 Aug 01
2
Common Power Management : NUT and HAL (stage 1)
...leep(2) in main-hal() to give time to
udev to set the perms). This might be due to the current script I'm
using on Debian, which mix hotplug and udev support (so shell script
exec is a bit slow!). Maybe using native udev rules would solve this.
* the current HAL namespace considers only battery/ac_adaptor, while
UPSs also have input, output, outlet, ... and various commands (see
[3])
4) For the brave who want to test
---------------------------------------------
* svn co svn://svn.debian.org/nut/branches/HAL
* install libhal-dev
* "./configure && make hal" from within the nut d...
2008 Jun 24
2
Fwd: DeviceKit-power patches
...ther, I would like that we (HAL/DK-p, GPM,
>> NUT, ...) discuss the variable naming, and more generally the scope of
>> DK-p.
>>
>> For the variable naming, I would like to propose a draft,
>> merging/modifying/extending the base from the current HAL battery /
>> ac_adaptor collections and NUT variables [1].
>
> Right.
>
>> My general idea (already exposed iirc) is to promote a "Power Module"
>> notion, composed of one or more power component (battery, input,
>
> Not input -- I think we should leave all input to INPUT and XOrg.
yo...