Mailing List Archive

www.netbsd.se

XOrg


List view - Thread view


Subject: Touchscreen on Panasonic CF-18

From: John R.

Date: 2006-05-18 03:26:32


Hello,

I am having difficulties getting the touchscreen on a Panasonic CF-18 Toughbook \ 
working in X (Version 7.0.99.903 (7.1.0 RC 3)).  I do not know if this is a \ 
problem at the OS level or with X.  This is not the digitizer (Wacom) version of \ 
the laptop.  Kernel 2.6.16.16 reports the following (not necessarily all \ 
touchscreen related):

PNP: PS/2 Controller [PNP0303:K101,PNP0f13:MOU2] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0c: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A

And later in the boot:

input: PS/2 Generic Mouse as /class/input/input1
input: PS/2 Generic Mouse as /class/input/input2

There is a lot of files created in these /sys entries.  I can provide details as \ 
needed.

/dev/input has the following:

crw-------  1 root root 13, 64 Feb 19 05:19 event0
crw-------  1 root root 13, 65 May 16 18:15 event1
crw-------  1 root root 13, 66 May 16 18:15 event2
crw-rw----  1 root root 13,  0 Oct 19  2005 js0
crw-rw----  1 root root 13,  1 Oct 19  2005 js1
crw-rw----  1 root root 13,  2 Oct 19  2005 js2
crw-rw----  1 root root 13,  3 Oct 19  2005 js3
crw-r--r--  1 root root 13, 63 Feb 11 04:26 mice
crw-r--r--  1 root root 13, 32 May 16 18:15 mouse0
crw-r--r--  1 root root 13, 33 May 16 18:15 mouse1
crw-rw----  1 root root 13, 35 Oct 19  2005 mouse3

evtest on event0 shows it is the keyboard.  event2 is the built in touchpad.  \ 
Both these generate events like one would expect.  evtest event1 (which I \ 
suspect is the touchscreen) yields:

Input driver version is 1.0.0
Input device ID: bus 0x11 vendor 0x2 product 0x1 version 0x0
Input device name: "PS/2 Generic Mouse"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 272 (LeftBtn)
    Event code 273 (RightBtn)
    Event code 274 (MiddleBtn)
  Event type 2 (Relative)
    Event code 0 (X)
    Event code 1 (Y)
Testing ... (interrupt to exit)

No events are generated when the display is touched.

I have tried the fpit driver (using various xorg.conf/setserial combinations).  \ 
The touchscreen works fine in Windows (reports device as Fujitsu touchscreen).

Any thoughts?

John
_______________________________________________
xorg mailing list
<email removed>
http://lists.freedesktop.org/mailman/listinfo/xorg

From: Mark Pustjens

Date: 2006-05-18 08:36:48



-- 
He remembered the knowledge. He remembered feeling his mind as cold as ice and
limitless as the night sky. He remembered being summoned into reluctant
existence at the moment the first creature lived, in the certain knowledge that
he would outlive life until the last being in the universe passed to its
reward, when it would be his job, figuratively speaking, to put the chairs on
the tables and turn all the lights off.
He remembered the loneliness.
   (Mort)

On Wed, 17 May 2006, John R. wrote:

> Hello,
>
> I am having difficulties getting the touchscreen on a Panasonic CF-18 \ 
Toughbook working in X (Version 7.0.99.903 (7.1.0 RC 3)).  I do not know if this \ 
is a problem at the OS level or with X.  This is not the digitizer (Wacom) \ 
version of the laptop.  Kernel 2.6.16.16 reports the following (not necessarily \ 
all touchscreen related):
>
> PNP: PS/2 Controller [PNP0303:K101,PNP0f13:MOU2] at 0x60,0x64 irq 1,12
> i8042.c: Detected active multiplexing controller, rev 1.1.
> serio: i8042 AUX0 port at 0x60,0x64 irq 12
> serio: i8042 AUX1 port at 0x60,0x64 irq 12
> serio: i8042 AUX2 port at 0x60,0x64 irq 12
> serio: i8042 AUX3 port at 0x60,0x64 irq 12
> serio: i8042 KBD port at 0x60,0x64 irq 1
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> 00:0c: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>
> And later in the boot:
>
> input: PS/2 Generic Mouse as /class/input/input1
> input: PS/2 Generic Mouse as /class/input/input2
>
> There is a lot of files created in these /sys entries.  I can provide \ 
details as needed.
>
> /dev/input has the following:
>
> crw-------  1 root root 13, 64 Feb 19 05:19 event0
> crw-------  1 root root 13, 65 May 16 18:15 event1
> crw-------  1 root root 13, 66 May 16 18:15 event2
> crw-rw----  1 root root 13,  0 Oct 19  2005 js0
> crw-rw----  1 root root 13,  1 Oct 19  2005 js1
> crw-rw----  1 root root 13,  2 Oct 19  2005 js2
> crw-rw----  1 root root 13,  3 Oct 19  2005 js3
> crw-r--r--  1 root root 13, 63 Feb 11 04:26 mice
> crw-r--r--  1 root root 13, 32 May 16 18:15 mouse0
> crw-r--r--  1 root root 13, 33 May 16 18:15 mouse1
> crw-rw----  1 root root 13, 35 Oct 19  2005 mouse3
>
> evtest on event0 shows it is the keyboard.  event2 is the built in \ 
touchpad.  Both these generate events like one would expect.  evtest event1 \ 
(which I suspect is the touchscreen) yields:
>
> Input driver version is 1.0.0
> Input device ID: bus 0x11 vendor 0x2 product 0x1 version 0x0
> Input device name: "PS/2 Generic Mouse"
> Supported events:
>  Event type 0 (Sync)
>  Event type 1 (Key)
>    Event code 272 (LeftBtn)
>    Event code 273 (RightBtn)
>    Event code 274 (MiddleBtn)
>  Event type 2 (Relative)
>    Event code 0 (X)
>    Event code 1 (Y)
> Testing ... (interrupt to exit)
>

To me it appears that the device was not recognised correctly. A 
touchscreen is an absolute pointer device, and here it shows that it is 
recognised as a relative pointer device.

> No events are generated when the display is touched.
>
> I have tried the fpit driver (using various xorg.conf/setserial \ 
combinations).  The touchscreen works fine in Windows (reports device as Fujitsu \ 
touchscreen).
>
> Any thoughts?
>
> John
> _______________________________________________
> xorg mailing list
> <email removed>
> http://lists.freedesktop.org/mailman/listinfo/xorg
>
_______________________________________________
xorg mailing list
<email removed>
http://lists.freedesktop.org/mailman/listinfo/xorg

From: John R.

Date: 2006-05-20 18:33:46


Thanks for the feedback...

I hacked at the kernel source (drivers/input/mouse/lifebook.c) in order 
do get the touchscreen seen as a touchscreen by the input system.  My 
shotgun approach also made the touchpad act like a touchscreen.  With 
this change, X was able to work with the touchscreen.  I tried evtouch, 
evdev, fpit and maybe another Driver.  They all acted generally the 
same.  Issues I had maybe were due to lack of calibration.

Maybe someone who knows what they are doing and has an interest in this 
could come up with the right solution.  I would be willing to give an 
implementation a try if someone could pass on the approach needed to 
have only one of two built-in pointing devices seen as a specific kind 
of pointing device.  The lifebook.c code uses DMI information to 
determine the model of laptop.  More granularity is needed.  Maybe there 
is a way to take action on something like the "Phys=" entry in 
/proc/bus/input/devices.

John
_______________________________________________
xorg mailing list
<email removed>
http://lists.freedesktop.org/mailman/listinfo/xorg

From: Antoine

Date: 2006-06-01 23:15:41


Hello world

I'm seeking to get in contact with John R who wrote a driver for the 
touchscreen of the panasonic CF-18. I have one of these babies and would 
enjoy to test his driver on it.

Best regards

Antoine Drouin
_______________________________________________
xorg mailing list
<email removed>
http://lists.freedesktop.org/mailman/listinfo/xorg