Re: webcamd based touchscreen problem on Pi3

On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote:
> This is what I have right now:
> [20]sa# cat /etc/X11/xorg.conf 
> 
> Section "InputDevice"
>         Identifier      "Touchscreen"
>         Driver          "evdev"
>         Option          "Device" "/dev/input/event0"
> EndSection
> 
> Section "ServerLayout"
>         Identifier      "MyLayout"
>         InputDevice     "Touchscreen"
> EndSection
> 
> 
> Unfortunately now I face the next problem.
> 
> [112753.535] (II) Using input driver 'evdev' for 'evdev touchscreen'
> [112753.536] (**) evdev touchscreen: always reports core events
> [112753.536] (**) evdev: evdev touchscreen: Device: "/dev/input/event0"
> [112753.598] (--) evdev: evdev touchscreen: Vendor 0xeef Product 0x5
> [112753.598] (--) evdev: evdev touchscreen: Found absolute axes
> [112753.598] (--) evdev: evdev touchscreen: Found absolute multitouch axes
> [112753.598] (II) evdev: evdev touchscreen: No buttons found, faking one.
> [112753.598] (--) evdev: evdev touchscreen: Found x and y absolute axes
> [112753.598] (--) evdev: evdev touchscreen: Found absolute touchscreen
> [112753.598] (II) evdev: evdev touchscreen: Configuring as touchscreen
> [112753.598] (**) evdev: evdev touchscreen: YAxisMapping: buttons 4 and 5
> [112753.598] (**) evdev: evdev touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> [112753.598] (II) XINPUT: Adding extended input device "evdev touchscreen" (type: TOUCHSCREEN, id 6)
> [112753.599] (II) evdev: evdev touchscreen: initialized for absolute axes.
> [112753.600] (**) evdev touchscreen: (accel) keeping acceleration scheme 1
> [112753.600] (**) evdev touchscreen: (accel) acceleration profile 0
> [112753.600] (**) evdev touchscreen: (accel) acceleration factor: 2.000
> [112753.600] (**) evdev touchscreen: (accel) acceleration threshold: 4
> [112753.601] (WW) fcntl(6, F_SETOWN): Invalid argument
> 
> [26]sa-moeller> xinput
>  Virtual core pointer                         id=2    [master pointer  (3)]
>     Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
>     Touchscreen                              id=6    [slave  pointer  (2)]
>     sysmouse                                 id=8    [slave  pointer  (2)]
>  Virtual core keyboard                        id=3    [master keyboard (2)]
>      Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
>      kbdmux                                   id=7    [slave  keyboard (3)]
> 
> Everything looks good so far, at least in my eyes.
> Well - wheel emulation and such sounds a bit strange, as if it is handled
> as a touchpad and not like a touchscreen.
> But it says type touchscreen, so I assume that's ok.
> However, I get no touch events.
> I've started xev fullscreen and still nothing.
> 
> Somewhere else I've read that /dev/input/event0 should deliver something
> if read and a touch happens, but this is not the case for me.
> 
> Any ideas how I can debug this thing?
> There was a reference somewhere about a commandline programm to run against
> an evdev, but I can't find it anymore.

xinput test delivers nothing on the touchscreen.

Neither evtest nor evdev-dump compiles because they are both missing
linux include files at some point.
https://cgit.freedesktop.org/~whot/evtest/
[48]sa> make
make  all-am
cc -DHAVE_CONFIG_H -I.      -g -O2 -MT evtest.o -MD -MP -MF .deps/evtest.Tpo -c -o evtest.o evtest.c
evtest.c:46:10: fatal error: 'linux/version.h' file not found
#include <linux/version.h>
         ^~~~~~~~~~~~~~~~~
1 error generated.
*** Error code 1

Stop.
make[1]: stopped in /home/ticso/evtest
*** Error code 1

Stop.
make: stopped in /home/ticso/evtest
Exit 1

https://github.com/gonzoua/evdev-dump/tree/freebsd
...
checking for unistd.h... yes
checking linux/input.h usability... no
checking linux/input.h presence... no
checking for linux/input.h... no
checking for /usr/include/linux/input.h... no
configure: error: /usr/include/linux/input.h not found
4.765u 3.954s 0:08.64 100.8%    31397+2201k 0+27io 0pf+0w
Exit 1

The touchscreen itself should be functional as it has a touch area outside
the display, which is interpreted by the USB controller to change the
backlight.
The exact same display also worked fine on Raspbian.

-- 
B.Walter <bernd_at_bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.