Problems when compiling plpevtch driver

Started by Tomy, November 14, 2009, 15:31:18 PM

Previous topic - Next topic

Tomy

When I try to compile the latest plpevtch driver on Ubuntu 09.10, I get the following error:

evdev.c: In function 'EvdevReadInput':
evdev.c:295: warning: passing argument 4 of 'TimerSet' from incompatible pointer type
/usr/include/xorg/os.h:192: note: expected 'OsTimerCallback' but argument is of type 'CARD32 (*)(struct _OsTimerRec *, CARD32,  struct _LocalDeviceRec *)'
evdev.c:371: warning: passing argument 4 of 'TimerSet' from incompatible pointer type
/usr/include/xorg/os.h:192: note: expected 'OsTimerCallback' but argument is of type 'CARD32 (*)(struct _OsTimerRec *, CARD32,  struct _LocalDeviceRec *)'
make[2]: *** [plpevtch_drv_la-evdev.lo] Error 1
make[2]: Leaving directory `/home/tom/xf86-input-plpevtch-0.4.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/tom/xf86-input-plpevtch-0.4.0'
make: *** [all] Error 2

Does anybody know what I'm doing wrong?

Cheers,
Tom


Elmar

hi,
its not your fault. i will update the driver soon to fix this problem with the new xorg sources.

regards
elmar

Tomy

Hi,

good news... and thanks for the fast answer!!

regards
Tom

Elmar

i planed to spend some time to fix it tomorrow or the day after

regards
elmar

Elmar


Tomy

I'm sorry for the troubles...
Cause I'm not really familiar with this topic, I can't really help, but I could Betatest if it would help.

sf

Did anyone ever resolve this problem? I'm getting the same error when installing this driver on Ubuntu Netbook Remix 9.10 on a Flybook V33i.

maddis

I got the driver compiled for Ubuntu 9.10 and also got it working. Although this is kludge and should be used with caution. I have one problem though. When touchscreen is working the keyboard and mouse stops working!

But here are the changes:

--- evdev.c     (revision 251)
+++ evdev.c     (working copy)
@@ -106,7 +106,7 @@
  * But I need it, even if it _is_ private.
  */

-void xf86ActivateDevice(InputInfoPtr pInfo);
+//void xf86ActivateDevice(InputInfoPtr pInfo);
int xold,yold;


This is the kludge part. I wasn't sure what I should put there so I just tested and with value 2 it seemed to work.
--- evdev_axes.c        (revision 251)
+++ evdev_axes.c        (working copy)
@@ -621,8 +621,7 @@

     if (!InitValuatorClassDeviceStruct(device, axes,
#if GET_ABI_MAJOR(ABI_XINPUT_VERSION) >= 1
-                                       GetMotionHistory,
-                                       GetMotionHistorySize(),
+                                      2,
#else
                                        miPointerGetMotionEvents,
                                        miPointerGetMotionBufferSize(),

Elmar

hi,
thanks. i will take a look at it.

best regards
elmar

Elmar

#9
hi,
i updated the touchscreen driver.  compiling with the current xorg sources works now. please test it.
http://www.plop.at/en/touchscreen.html

regards
elmar

Arobase

#10
The mouse and keyboard issue still exist when touchscreen is active in the last version of the drivers... ^^

I had to comment out " InputDevice "touchscreen" "Pointer"" in the ServerLayout section to solve the problem.

Edit : Sorry, bad sentence ! I had to comment " InputDevice "touchscreen" "Pointer"" in the ServerLayout section to solve the problem." ^^
On my computer if this line exist in ServerLayout section, I can't use the mouse and the keyboard.
When removed, everything works...  :P

almeo

I have the same problem : my keyboard (but not my touchpad) is inactivated
when I activate the plpevtch driver...
I am using the xorg1.7 from debian, and I first tried with my 2.6.30 kernel, then I
managed to rebuild psb kernel driver for 2.6.32 and I tried again, and it is still the
same problem...
I am using the 5.0 version of plpevtch compiled against Xorg1.7.

I would like to use the plpevtch driver because until now it has been the only one I
was able to calibrate without any problem...

Please, if some of you has any idea about the cause of the problem, I would be
glad  to know   :)

Elmar

hmm, i try to reproduce this problem here when i have time.

regards
elmar