Changes between Version 2 and Version 3 of Gen9A101TurboICSLinuxNotes

Timestamp:

09/14/13 16:31:44 (3 years ago)

Author:

comphuter

Comment:

--

Gen9A101TurboICSLinuxNotes

@@ -206 +206 @@
 The A101 G9 Turbo was shipped with two different touchscreens. The kernel module ''pixcir_i2c_tsp'' or ''tr16c0-i2c'' is needed, respectively, for the system to recognize the specific touchscreen.
 
-'''Note:''' Because my A101 G9 has a Touchplus TR16C0, I can only provide information for devices using the tr16c0-i2c driver. However, both of them support the following events: ''EV_SYN, EV_KEY, ABS_MT_SLOT, ABS_MT_POSITION_X, ABS_MT_POSITION_Y'' and ''ABS_MT_TRACKING_ID''. Additionally, pixcir based devices provide the events ''ABS_MT_TOUCH_MAJOR'' and ''ABS_MT_WIDTH_MAJOR'' (and possibly also ''ABS_MT_TOUCH_MINOR''). This information was extracted from the tr16c0/pixcir kernel code.
-
-=== Getting the touchscreen to work: Kernel driver ===
+'''Note:''' Because my A101 G9 has a Touchplus TR16C0, I can only provide information for devices using the tr16c0-i2c driver. However, both of them support the following events: ''EV_SYN, EV_KEY, ABS_MT_SLOT, ABS_MT_POSITION_X, ABS_MT_POSITION_Y'' and ''ABS_MT_TRACKING_ID''. I could provide an additional ABS_X/Y for the pixcir touchscreen like I provided for tr16c0, but I can't test it.
+
+=== Getting the touchscreen to work: Kernel driver (TR16C0) ===
+
+==== Basic setup ====
 
 In case of a Touchplus TR16C0, you should find messages similar to this one in your ''dmesg'' output after loading the ''tr16c0-i2c'' module:
 
-'''Note:''' There might also be some messages like ''tr16c0_i2c_tsp 4-005c: ping ?'' and ''tr16c0_i2c_tsp 4-005c: could not talk to tsp.)''. It is safe to ignore them as long as these last lines indicate that it detected an input-device.
+'''Note:''' There might also be some messages like ''tr16c0_i2c_tsp 4-005c: ping ?'' and ''tr16c0_i2c_tsp 4-005c: could not talk to tsp.)''. It is safe to ignore them as long as these last lines indicate that ed an input-device.
 {{{
 tr16c0_i2c_tsp 4-005c: trying v2 fw
@@ -256 +258 @@
 }}}
 
-Now there is just one issue left to address: Depending on whether you plugged in some other USB devices (e.g. a USB keyboard, or a USB hub with some other input devices) that also create event interfaces, your device might not be called ''/dev/input/event6'' all the time, though you might have some scripts that rely on it). You might want to create a symlink (in case of a static /dev, or via init-scripts) or let udev create a symlink (in case of a devtmpfs with udev). Usually, modern linux distributions use udev, so you just have to create a new file in ''/etc/udev/rules.d/'', containing something like this:
+==== Optional: Patch the driver for xf86-input-evdev compatibility ====
+
+Because the ''tr16c0-i2c'' driver does not report any (single-touch) ABS_X/Y events to the system, but only (multi-touch) ABS_MT_* events, it is necessary to patch the kernel driver for the [http://cgit.freedesktop.org/xorg/driver/xf86-input-evdev/ xf86-input-evdev] xorg driver to work, as it expects ABS_X/Y events for backwards compatibility reasons (older single-touch screens). Also, though that does not apply to the tr16c0 driver because it just populates all processed touch signals as finger touch events, ABS_X/Y is used for pen inputs, while the multitouch resources are used for finger touch input (TODO?)
+
+The following [http://4s0.de/~compi/archos-dev/patches/tr16c0-generate-abs-events.patch patch] addresses this issue.
+
+==== Optional: Setting up a symlink  to the input device via udev ====
+
+Depending on whether you plugged in some other USB devices (e.g. a USB keyboard, or a USB hub with some other input devices) that also create event interfaces, your device might not be called ''/dev/input/event6'' all the time, though you might have some scripts that rely on it). You might want to create a symlink (in case of a static /dev, or via init-scripts) or let udev create a symlink (in case of a devtmpfs with udev). Usually, modern linux distributions use udev, so you just have to create a new file in ''/etc/udev/rules.d/'', containing something like this:
 
 {{{
@@ -262 +272 @@
 }}}
 
-This udev rule creates a symlink pointing from ''/dev/input/touchscreen'' to the respective ''eventX'' device.
+This udev rule creates a symlink pointing from ''/dev/input/touchscreen'' to the respective ''eventX'' device.
 
 You are now ready to use it with Xorg.
@@ -269 +279 @@
 
 There are different input drivers available (these are just the one I tried):
- * [http://cgit.freedesktop.org/xorg/driver/xf86-input-evdev/ xf86-input-evdev]: The well-known event device input driver usually found on every base system with Xorg.
+ * [http://cgit.freedesktop.org/xorg/driver/xf86-input-evdev/ xf86-input-evdev]: The well-known event device input driver usually found on every base system with Xorg.
  * [http://gitorious.org/xf86-input-mtev/ xf86-input-mtev]: A multitouch event driver developed by MeeGo. It uses [http://bitmath.org/code/mtdev/ mtdev] for processing multitouch events.
  * [http://bitmath.org/code/multitouch/ xf86-input-multitouch]: A multitouch touchpad driver.
 
-''xf86-input-evdev'' will crash for both touchscreens, because none of them export ''ABS_X/Y'' events, but evdev assumes that there is a normal axis for every multitouch axis. This is not the case for Pixcir and TR16C0 touchscreens, as they only export ''ABS_MT_*'' axes, no ''ABS_*'' axes. Therefore it will crash at the moment you touch the sreen after starting X.
+==== xf86-input-evdev ====
+
+'''Note:''' ''xf86-input-evdev'' will not work unless you patch your kernel driver.
+
+xf86-input-evdev is one of the default Xorg input drivers. The main advantage is that most utilities work together with it, like touchegg (and therefore kde multitouch gestures, which is just a fork of touchegg), because ist just reports the plain events to the userland.
+
+Put the following code into a file in ''/etc/X11/xorg.conf.d/'':
+
+{{{
+Section "InputClass"
+    Identifier "Archos Touchscreen"
+    MatchProduct "tr16c0_i2c_tsp"
+    Option "Ignore" "off"
+    Option "CorePointer" "on"
+    Driver "evdev"
+EndSection
+}}}
+
+It should work right out of the box. Enjoy!
+
+==== xf86-input-mtev ====
 
 ''xf86-input-mtev'' should work for TR16C0, by using the [https://build.pub.meego.com/package/show?package=xorg-x11-drv-mtev&project=Project%3AKDE%3AMer_Extras patches of the MeeGo community]. If these don't work there is also another [http://oe-lite.org/redmine/projects/xorg/repository/revisions/master/show/recipes/xorg-driver/xf86-input-mtev patchset on OE-lite].
 
+
+
 '''Note:''' The latter one worked in my case. Also, I still have to test whether xf86-input-mtev is aware of multitouch gestures.
-
-''xf86-input-multitouch'' usually out of the box without problems, though it is a '''touchpad''' driver and therefore your touchscreen will only be usable like a trackpad/touchpad (i.e. a relative pointer device). This should usually be your last choice, if no other driver works.
-
-'''Note:''' xf86-input-multitouch supports multitouch gestures really well. In any case you might have interest to take a look into it.
 
 Now, here is an example xorg-config snippet usable by xorg.conf.d-automagic configuration:
@@ -292 +320 @@
     Option "CorePointer" "on"
     Driver "mtev"
-    #Driver "evdev"
-    #Driver "multitouch"
 EndSection
 }}}
 
-'''Note:''' Depending on your choice and the problems you drive into, you might want change the driver line.
-
-If everything is done right, the relevant part in your ''/var/log/Xorg.0.log'' should look similar to this:
-
-{{{
-[  4938.429] (II) config/udev: Adding input device tr16c0_i2c_tsp (/dev/input/event6)
-[  4938.429] (**) tr16c0_i2c_tsp: Applying InputClass "Archos Touchscreen"
-[  4938.429] (II) LoadModule: "mtev"
-[  4938.430] (II) Loading /usr/lib/xorg/modules/input/mtev_drv.so
-[  4938.430] (II) Module mtev: vendor="Nokia"
-[  4938.430]    compiled for 1.12.3, module version = 0.1.12
-[  4938.430]    Module class: X.Org XInput Driver
-[  4938.430]    ABI class: X.Org XInput driver, version 16.0
-[  4938.430] (II) Using input driver 'mtev' for 'tr16c0_i2c_tsp'
-[  4938.430] (**) Option "CorePointer" "on"
-[  4938.430] (**) tr16c0_i2c_tsp: always reports core events
-[  4938.430] (**) tr16c0_i2c_tsp: always reports core events
-[  4938.430] (**) Option "config_info" "udev:/sys/devices/virtual/input/input9/event6"
-[  4938.431] (II) XINPUT: Adding extended input device "tr16c0_i2c_tsp" (type: TOUCHSCREEN, id 8)
-[  4938.431] (II) device control: init
-[  4938.431] (**) Option "Device" "/dev/input/event6"
-[  4938.431] (II) mtev: caps: mtdata tracking_id position_x position_y
-[  4938.431] (II) mtev: tracking_id: 0 65535
-[  4938.431] (II) mtev: position_x: 0 1280
-[  4938.431] (II) mtev: position_y: 0 800
-[  4938.657] (II) pointer_control
-[  4938.657] (**) tr16c0_i2c_tsp: (accel) keeping acceleration scheme 1
-[  4938.657] (II) pointer_property
-[  4938.658] (II) pointer_property
-[  4938.658] (**) tr16c0_i2c_tsp: (accel) acceleration profile 0
-[  4938.658] (II) pointer_property
-[  4938.658] (II) pointer_property
-[  4938.658] (**) tr16c0_i2c_tsp: (accel) acceleration factor: 2.000
-[  4938.658] (**) tr16c0_i2c_tsp: (accel) acceleration threshold: 4
-[  4938.658] (II) device control: on
-}}}
+==== Testing your input driver ====
 
 Now you can test your display by running ''xinput'' in a terminal. First you call ''xinput list'' to list all the available input devices, then you test it:
@@ -353 +344 @@
 }}}
 
-'''Note:''' Depending on the input driver, testing the device will spit out completely different lines. This test output was generated by simply touching the screen on one freely selected point, releasing it directly after (i.e. a finger-click).
-
 Now you're done, your touchscreen is set up!