Dnia 2014-07-10, czw o godzinie 14:44 -0400, Benjamin Tissoires pisze: [..] Hi Benjamin, > However, I did not backport the speed attribute and the ac power > device (which > is infered by the battery status). I don't know if there are users of > those two, > so I let them aside for now. Przemo, any ideas if this is actually > used? Both tablets that I had (Graphire Wireless and Intuos4 Wireless) supports slow and fast reporting. Slow reporting is necessary with older bluetooth receivers otherwise the lag between pen movement and cursor movement made devices unusable. I tried to expose all events reported by hardware and I think AC reporting should stay in the kernel. Intuos4 Wireless AC power disconnected: bash-4.2$ cat /sys/class/power_supply/wacom_ac/uevent POWER_SUPPLY_NAME=wacom_ac POWER_SUPPLY_PRESENT=0 POWER_SUPPLY_ONLINE=0 POWER_SUPPLY_SCOPE=Device bash-4.2$ cat /sys/class/power_supply/wacom_battery/uevent POWER_SUPPLY_NAME=wacom_battery POWER_SUPPLY_PRESENT=1 POWER_SUPPLY_CAPACITY=85 POWER_SUPPLY_SCOPE=Device POWER_SUPPLY_STATUS=Discharging AC power connected: bash-4.2$ cat /sys/class/power_supply/wacom_ac/uevent POWER_SUPPLY_NAME=wacom_ac POWER_SUPPLY_PRESENT=1 POWER_SUPPLY_ONLINE=1 POWER_SUPPLY_SCOPE=Device bash-4.2$ cat /sys/class/power_supply/wacom_battery/uevent POWER_SUPPLY_NAME=wacom_battery POWER_SUPPLY_PRESENT=1 POWER_SUPPLY_CAPACITY=85 POWER_SUPPLY_SCOPE=Device POWER_SUPPLY_STATUS=Charging -- Kind regards, Przemo Firszt -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html