Just one fix - some kernels invalidate the device late after resume, leaving
us with dead devices. This issue is addressed by reopening the device if a
read error occurs.
Peter Hutterer (2):
Attempt to re-open devices on read errors.
evdev 2.0.5
git tag: xf86-input-evdev-2.0.5
http://xorg.freedesktop.org/archive/individual/driver/xf86-input-evdev-2.0.5.tar.bz2
MD5: aabf047629d279b0eb4cd236b9de3121 xf86-input-evdev-2.0.5.tar.bz2
SHA1: 9b6b77e6d9aa9bfbe0b7a31d4d070c0f6d372311 xf86-input-evdev-2.0.5.tar.bz2
http://xorg.freedesktop.org/archive/individual/driver/xf86-input-evdev-2.0.5.tar.gz
MD5: cdca14fa2fd7daffcb3c8d459e480b4c xf86-input-evdev-2.0.5.tar.gz
SHA1: 801bb0c74803e61d65868fe61198840a2e1aa465 xf86-input-evdev-2.0.5.tar.gz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :
http://lists.freedesktop.org/archives/xorg-announce/attachments/20080919/41f591de/attachment.pgp