Update documentation to mention evdev ioctls

martinpitt · Feb 20, 2013 · 6dcdffb · 6dcdffb
1 parent e29d6bc
commit 6dcdffb
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 13 deletions.
diff --git a/README.rst b/README.rst
@@ -10,12 +10,13 @@ access to the affected hardware.
 
 The ``UMockdevTestbed`` class builds a temporary sandbox for mock devices.
 Right now this covers sysfs, uevents, basic support for /dev devices, and
-recording/mocking usbdevfs ioctls (for PtP/MTP devices), but other aspects will
+recording/mocking usbdevfs (for PtP/MTP devices) and evdev (touch pads, Wacom
-be added in the future. You can add a number of devices including arbitrary
+tablets, etc.) ioctls, but other aspects will be added in the future. You can
-sysfs attributes and udev properties, and then run your software in that test
+add a number of devices including arbitrary sysfs attributes and udev
-bed that is independent of the actual hardware it is running on.  With this you
+properties, and then run your software in that test bed that is independent of
-can simulate particular hardware in virtual environments up to some degree,
+the actual hardware it is running on.  With this you can simulate particular
-without needing any particular privileges or disturbing the whole system.
+hardware in virtual environments up to some degree, without needing any
+particular privileges or disturbing the whole system.
 
 You can use this from the command line, and a wide range of programming
 languages (C, Vala, and everything which supports gobject-introspection, such

diff --git a/src/umockdev.vala b/src/umockdev.vala
@@ -25,13 +25,13 @@ namespace UMockdev {
  *
  * The #UMockdevTestbed class builds a temporary sandbox for mock devices.
  * Right now this covers sysfs, uevents, basic support for /dev devices, and
- * recording/mocking usbdevfs ioctls (for PtP/MTP devices), but other aspects
+ * recording/mocking usbdevfs (for PtP/MTP devices) and evdev (touch pads,
- * will be added in the future.  You can add a number of devices including
+ * Wacom tablets, etc.) ioctls, but other aspects will be added in the future.
- * arbitrary sysfs attributes and udev properties, and then run your software
+ * You can add a number of devices including arbitrary sysfs attributes and
- * in that test bed that is independent of the actual hardware it is running
+ * udev properties, and then run your software in that test bed that is
- * on.  With this you can simulate particular hardware in virtual environments
+ * independent of the actual hardware it is running on.  With this you can
- * up to some degree, without needing any particular privileges or disturbing
+ * simulate particular hardware in virtual environments up to some degree,
- * the whole system.
+ * without needing any particular privileges or disturbing the whole system.
  *
  * You can either add devices by specifying individual device paths,
  * properties, and attributes, or use the umockdev-record tool to create a human