Permalink
Browse files

Update documentation to mention evdev ioctls

  • Loading branch information...
1 parent e29d6bc commit 6dcdffbdbf157906315294900374423148132094 Martin Pitt committed Feb 20, 2013
Showing with 14 additions and 13 deletions.
  1. +7 −6 README.rst
  2. +7 −7 src/umockdev.vala
View
@@ -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
-be added in the future. You can add a number of devices including arbitrary
-sysfs attributes and udev properties, and then run your software in that test
-bed that is independent of the actual hardware it is running on. With this you
-can simulate particular hardware in virtual environments up to some degree,
-without needing any particular privileges or disturbing the whole system.
+recording/mocking usbdevfs (for PtP/MTP devices) and evdev (touch pads, Wacom
+tablets, etc.) ioctls, but other aspects will be added in the future. You can
+add a number of devices including arbitrary sysfs attributes and udev
+properties, and then run your software in that test bed that is independent of
+the actual hardware it is running on. With this you can simulate particular
+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
View
@@ -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
- * will be added in the future. You can add a number of devices including
- * arbitrary sysfs attributes and udev properties, and then run your software
- * in that test bed that is independent of the actual hardware it is running
- * on. With this you can simulate particular hardware in virtual environments
- * up to some degree, without needing any particular privileges or disturbing
- * the whole system.
+ * recording/mocking usbdevfs (for PtP/MTP devices) and evdev (touch pads,
+ * Wacom tablets, etc.) ioctls, but other aspects will be added in the future.
+ * You can add a number of devices including arbitrary sysfs attributes and
+ * udev properties, and then run your software in that test bed that is
+ * independent of the actual hardware it is running on. With this you can
+ * simulate particular hardware in virtual environments up to some degree,
+ * 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

0 comments on commit 6dcdffb

Please sign in to comment.