[ANNOUNCE] xf86-input-elographics 1.3.0

2011-06-26 Thread Peter Hutterer
This driver is one of the legacy input drivers that you almost certainly don't want to use. Use the kernel driver instead (if one exists) or write one (if none exists). This release brings the usual input ABI updates, cleanups, etc. and one real bugfix. This release requires server 1.10 for the

Re: Evdev problem with keyboard

2011-06-26 Thread Peter Hutterer
On Sat, Jun 25, 2011 at 06:56:14PM +0100, Scott Waye wrote: I have a bluetooth Logitech diNovo Edge keyboard (with mouse pad) which I'm trying to get working using the evdev driver. I believe the bluetooth part is working fine as I get two devices in /dev/input . If I cat /dev/input/event5 I

Re: Evdev problem with keyboard

2011-06-26 Thread Markus Strobl
On 06/26/2011 05:58 PM, Peter Hutterer wrote: On Sat, Jun 25, 2011 at 06:56:14PM +0100, Scott Waye wrote: I have a bluetooth Logitech diNovo Edge keyboard (with mouse pad) which I'm trying to get working using the evdev driver. I believe the bluetooth part is working fine as I get two devices

[ANNOUNCE] xf86-input-fpit 1.4.0

2011-06-26 Thread Peter Hutterer
This driver is one of the legacy input drivers that you almost certainly don't want to use. Use the kernel driver instead (if one exists) or write one (if none exists). This release brings the usual input ABI updates, cleanups, etc. and one real bugfix. 1.4.0 has actually seen testing in the form

[ANNOUNCE] xf86-input-elographics 1.3.0

2011-06-26 Thread Peter Hutterer
This driver is one of the legacy input drivers that you almost certainly don't want to use. Use the kernel driver instead (if one exists) or write one (if none exists). This release brings the usual input ABI updates, cleanups, etc. and one real bugfix. This release requires server 1.10 for the

[ANNOUNCE] xf86-input-hyperpen 1.4.0

2011-06-26 Thread Peter Hutterer
This driver is one of the legacy input drivers and if you know users of this driver you might want to put them under a display cabinet in a museum because they must have rarity value by now. There has been exactly one fix (in 2007) to this driver since the modularisation in 2003. Use the kernel