All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Weninger <max.weninger@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: SOLVED support of touchscreen reported as eGalax but is not working
Date: Tue, 27 Jan 2009 02:05:29 +0100	[thread overview]
Message-ID: <20090127020529.4070840b@zork.foo.com> (raw)
In-Reply-To: <20090127014822.780ecb90@zork.foo.com>

[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]

Hi again

On Tue, 27 Jan 2009 01:48:22 +0100
Max Weninger <max.weninger@gmail.com> wrote:

> On Tue, 27 Jan 2009 01:38:06 +0100
> Max Weninger <max.weninger@gmail.com> wrote:
> 
> > 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
> 
> It also works with 2.6.26.8

After comparing the usbtouchscreen.c sources between the different
versions I got it working by commenting the follwoing lines

...
#ifdef CONFIG_TOUCHSCREEN_USB_EGALAX
        /* ignore the HID capable devices, handled by usbhid */
        {USB_DEVICE_HID_CLASS(0x0eef, 0x0001), .driver_info = DEVTYPE_IGNORE},
        {USB_DEVICE_HID_CLASS(0x0eef, 0x0002), .driver_info = DEVTYPE_IGNORE},
...

Now the entry in /proc/bus/input/devices is created as in the
older versions.

So it seems that usbhid is not correctly handling my type
of touchscreen if I understand the comment there correctly

Regards

Max

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-01-27  1:05 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
2009-01-27  0:48         ` Max Weninger
2009-01-27  1:05           ` Max Weninger [this message]
2009-01-30 23:18             ` SOLVED " 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=20090127020529.4070840b@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.