Hi All,

The Xorg configuration, tat worked for me is as follows

Section "InputClass"
    Identifier "ChelongTouch"
    MatchProduct "eGalax Inc. USB TouchController"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    Option "Resolution" "1024 0 600 0"
    Option    "Calibration"    "1988 56 143 1936"
    MatchIsTouchscreen "on"
    Option    "SwapAxes"    "0"
EndSection

I took this conf from the discussion in below link
https://bugs.tizen.org/jira/browse/TIVI-679

And calibration value is given by the xinput_calibrator tool

Thanks a lot for everyone ...

Regards,
Prabhuram M



On Fri, Sep 6, 2013 at 1:19 PM, Chang, Esmond <[email protected]>wrote:

>  Did you try to use the mtev driver? As I know, touch device should use
> mtev driver instead of evdev.****
>
> ** **
>
> Regards,****
>
> Esmond****
>
> ** **
>
> *From:* [email protected] [mailto:[email protected]] *On
> Behalf Of *Prabhuram Murugan
> *Sent:* Friday, September 06, 2013 10:39 AM
>
> *To:* Clark, Joel
> *Cc:* IVI Tizen
> *Subject:* Re: egalax touch screen not detected by X****
>
> ** **
>
>
> I extracted the binary file from TIZEN 1.0 rpm,
>
> xinput_calibrator --list
> No calibratable devices found.****
>
> it is not able find any touch device. I think this is because it is
> detected as a mouse device .****
>
>
> And the Xorg log file in /var/log/Xorg.0.log shows the below log,****
>
>
> [    10.434] (II) config/udev: Adding input device eGalax Inc. USB
> TouchController (/dev/input/mouse1)
> [    10.434] (II) No input driver specified, ignoring this device.
> [    10.434] (II) This device may have been added with another device file.
> ****
>
> I am wondering if the values in my Xorg configuration file is proper ?
>
> Section "InputClass"
>         Identifier "eGalax Inc. USB TouchController"
>         MatchIsPointer "on"
>         MatchDevicePath "/dev/input/event*"
>         Option "Calibration" "17 1000 27 1000"
>         Driver "evdev"
> EndSection****
>
> Jeol,****
>
> it may sound stupid,****
>
> Actually I launched a application and touched across the entire touch
> screen ...****
>
> Screen was filled with buttons, but non of them received any click event...
> ****
>
> ** **
>
> Regards,****
>
> Prabhuram M****
>
> ** **
>
> ** **
>
> On Fri, Sep 6, 2013 at 9:53 AM, Clark, Joel <[email protected]> wrote:*
> ***
>
> I’ll question my on assertion, Should evdev recognize a “single point,
> resistive touch screen device”, as a USB Mouse or as some other device?
> For multi-touch we know mouse did not work. But I think it also did not
> work for single touch, where when it was treated as a mouse, we could swipe
> (“drag” like a mouse), but could not tap (“click” like a mouse).****
>
>  ****
>
> Regards****
>
> Joel****
>
>  ****
>
>  ****
>
> *From:* Clark, Joel
> *Sent:* Thursday, September 05, 2013 5:46 PM
> *To:* Rees, Kevron M; Prabhuram Murugan
> *Cc:* IVI Tizen
> *Subject:* RE: egalax touch screen not detected by X****
>
>  ****
>
> It sounds like the same bug as in Wayland.  It is being recognized as a
> USB device, but not as a touchscreen, so it defaults to being a mouse,
> which it is not. ****
>
>  ****
>
> When you say “touch input is not working with this board”, what
> specifically is the failure mode? Does it respond to taps at all?  Does it
> respond to “drag” at all?****
>
>  ****
>
> Regards****
>
> Joel****
>
>  ****
>
>  ****
>
> *From:* [email protected] 
> [mailto:[email protected]<[email protected]>]
> *On Behalf Of *Rees, Kevron****
>
>
> *Sent:* Thursday, September 05, 2013 5:41 PM
> *To:* Prabhuram Murugan****
>
> *Cc:* IVI Tizen
> *Subject:* Re: egalax touch screen not detected by X****
>
>  ****
>
> it sounds like it is being recognized.  perhaps it just needs
> calibration?  I recall there is an xinput_calibrator tool that you might be
> able to use to calibrate it.  I don't remember if that tool was included in
> Tizen 2.0 though.****
>
> -Kevron****
>
>  ****
>
> On Thu, Sep 5, 2013 at 5:03 PM, Prabhuram Murugan <
> [email protected]> wrote:****
>
> Hi All,****
>
> I am using TIZEN 2.0 ...****
>
> Jeol,****
>
>  ****
>
> I gone through the changes, https://review.tizen.org/gerrit/#/c/6047/ ,
> but it is for Weston and TIZEN 3.0
>
> however to fix this issues in TIZEN 2.0, I am looking in to
> adaptation/xorg/driver/xserver-xorg-input-evdev
>
> can you advice, if this is the right point to start ,
>
> Rusty,****
>
> Yes, we are using a single point, resistive touch screen device.****
>
> and from the mount point */dev/input/mouse1* looks it is detected as the
> mouse device.****
>
> TIZEN 2.0 doesnt support single touch device ? ****
>
>  ****
>
>  ****
>
> On Fri, Sep 6, 2013 at 2:52 AM, Abramski, Adam M <
> [email protected]> wrote:****
>
> I believe he mentions below that he's running 2.0, NOT 3.0.
> Adam****
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Rusty Lynch
> Sent: Thursday, September 05, 2013 8:58 AM
> To: Clark, Joel
> Cc: IVI Tizen
> Subject: Re: egalax touch screen not detected by X
>
> Actually... that fix only applies when you are using wayland.
>
> I'm not sure if you were using a touchscreen with the same issue, but we
> hit an issue when a vendor wired up an old style single point resistive
> screen on top of an egalax touchscreen controller, where weston didn't
> recognize the device as touch (since it didn't support the modern
> multipoint protocol), and treated it as a mouse, but then the device would
> emit TOUCH_BTN instead of a left or right mouse button.
>
> So... it actually worked, but no software is listening for this little
> known button value so kind of pointless.
>
>     --rusty
>
> On Thu, 2013-09-05 at 14:21 +0000, Clark, Joel wrote:
> > This has been fixed in Tizen IVI 3.0
> >  https://bugs.tizen.org/jira/i#browse/TIVI-1086
> >
> >
> >
> > You might want to look at these patches:
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=54428
> >
> >
> >
> > https://review.tizen.org/gerrit/#/c/6047/
> >
> >
> >
> > with the fix the touchscreen is no longer recognized as a mouse
> > device.
> >
> >
> >
> > Regards
> >
> > Joel
> >
> >
> >
> >
> >
> > From: [email protected] [mailto:[email protected]]
> > On Behalf Of Prabhuram Murugan
> > Sent: Thursday, September 05, 2013 5:38 AM
> > To: IVI Tizen
> > Subject: egalax touch screen not detected by X
> >
> >
> >
> > Hi ,
> >
> >
> > I am using a USB based touch screen LCD for TIZEN on NDiS 166 board.
> >
> >
> > But the touch input is not working with this board.
> > I came across many bugs raised in TIZEN bug site, but they are mostly
> > for touch calibration.
> >
> >
> > In my case the touch screen is detected by the kernel but "xinput
> > list" doesnt list my touch screen device at all. Below are dmesg and
> > xinput list logs ....
> >
> >
> > I am using TIZEN 2.0 release.
> >
> >
> >
> >
> >
> > DMESG
> >
> >
> > [   12.703678] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> > [   21.528514] composite sync not supported
> > [  884.484925] usb 2-1.1: USB disconnect, device number 3 [
> > 885.940235] usb 2-1.1: new low-speed USB device number 7 using
> > ehci-pci [  886.020179] usb 2-1.1: New USB device found,
> > idVendor=0eef,
> > idProduct=0001
> > [  886.020184] usb 2-1.1: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=0
> > [  886.020188] usb 2-1.1: Product: USB TouchController [  886.020191]
> > usb 2-1.1: Manufacturer: eGalax Inc.
> > [  886.022735] input: eGalax Inc. USB TouchController as
> > /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input9
> >
> > -sh-4.1# xinput list
> > ⎡ Virtual core pointer                        id=2    [master pointer
> > (3)]
> > ⎜   ↳ Virtual core XTEST pointer                  id=4    [slave
> > pointer  (2)]
> > ⎜   ↳ SEJIN SEJIN USB Mini Trackball Keyboard     id=11    [slave
> > pointer  (2)]
> > ⎣ Virtual core keyboard                       id=3    [master keyboard
> > (2)]
> >     ↳ Virtual core XTEST keyboard                 id=5    [slave
> > keyboard (3)]
> >     ↳ SEJIN SEJIN USB Mini Trackball Keyboard     id=10    [slave
> > keyboard (3)]
> > ∼ Power Button                                id=6    [floating slave]
> > ∼ Video Bus                                   id=7    [floating slave]
> > ∼ Power Button                                id=8    [floating slave]
> > ∼ Microsoft LifeCam VX-800                    id=9    [floating slave]
> >
> > #cat /dev/input/mouse1
> >
> > )9
> >
> >
> >
> >
> > Thanks and Regards,
> > Prabhuram M
> >
> >
> > _______________________________________________
> > IVI mailing list
> > [email protected]
> > https://lists.tizen.org/listinfo/ivi
>
>
> _______________________________________________
> IVI mailing list
> [email protected]
> https://lists.tizen.org/listinfo/ivi
> _______________________________________________
> IVI mailing list
> [email protected]
> https://lists.tizen.org/listinfo/ivi****
>
>  ****
>
>
> _______________________________________________
> IVI mailing list
> [email protected]
> https://lists.tizen.org/listinfo/ivi****
>
>  ****
>
> ** **
>
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi

Reply via email to