From: Max Weninger <max.weninger@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: support of touchscreen reported as eGalax but is not working
Date: Tue, 27 Jan 2009 01:38:06 +0100 [thread overview]
Message-ID: <20090127013806.5e31199f@zork.foo.com> (raw)
In-Reply-To: <497DA8E3.5070006@wincor-nixdorf.com>
[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]
Hi
On Mon, 26 Jan 2009 13:13:23 +0100
Niels de Vos <niels.devos@wincor-nixdorf.com> wrote:
> Max Weninger wrote:
> > Niels de Vos <niels.devos@wincor-nixdorf.com> wrote:
> >> You can obviously download the drivers from
> >> <http://home.eeti.com.tw/web20/TouchKitDriver/linuxDriver.htm>.
> >>
> >> It would be great if eGalax could be convinced to get these drivers
> >> included in main-line ;)
> >
> > Thanks for your quick reply
> > BUT: I have tried those driver also
> >
> > I tried this "brandnew" one (but also older ones)
> > http://home.eeti.com.tw/web20/drivers/touch_driver/Linux/2.06.2416/TouchKit-2.06.2410-32b-k26.tar.gz
> > after making it compile for 2.6.28.2 :)
> > since there is source code delivered
>
> For what it's worth; the version we use from eGalax is 1.0.3.1701. I
> don't have the hardware here atm, so I can't test an other driver
> now.
I tried kernel 2.6.23.17 and there the touchscreen is recognized
using the builtin usbtouchscreen driver
/proc/bus/usb/devices delivers
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0eef ProdID=0001 Rev= 1.00
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 44mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbtouchscreen
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=5ms
and
/proc/bus/input/devices
I: Bus=0003 Vendor=0eef Product=0001 Version=0100
N: Name="USB Touchscreen 0eef:0001"
P: Phys=usb-0000:00:1d.0-2/input0
S: Sysfs=/class/input/input3
U: Uniq=
H: Handlers=mouse2 event3
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=3
I also tried to blacklist the usbhid with 2.6.28.2
then it display Driver=usbtouchscreen in /proc/bus/usb/devices
but still no entry in /proc/bus/input/devices
Any ideas?
Regards
max
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-27 0:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 22:49 support of touchscreen reported as eGalax but is not working Max Weninger
2009-01-26 10:46 ` Niels de Vos
2009-01-26 11:49 ` Max Weninger
2009-01-26 12:13 ` Niels de Vos
2009-01-27 0:38 ` Max Weninger [this message]
2009-01-27 0:48 ` Max Weninger
2009-01-27 1:05 ` SOLVED " Max Weninger
2009-01-30 23:18 ` Andrew Morton
2009-01-31 22:09 ` Max Weninger
2009-02-03 6:59 ` Andrew Morton
2009-02-03 23:44 ` Daniel Ritz
2009-02-04 21:59 ` Max Weninger
2009-02-08 16:01 ` Daniel Ritz
2009-02-09 22:46 ` REALLY " Max Weninger
2009-02-02 13:39 ` Niels de Vos
2009-02-02 22:42 ` Max Weninger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090127013806.5e31199f@zork.foo.com \
--to=max.weninger@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.