public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Ritz <daniel.ritz@gmx.ch>
To: Christian Loitsch <lkml@abc.delta64.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: eGalax TouchScreen
Date: Mon, 12 Oct 2009 12:17:13 +0200	[thread overview]
Message-ID: <4AD30229.6090607@gmx.ch> (raw)
In-Reply-To: <200910082219.43160.lkml@abc.delta64.com>

hi Christian

On 08.10.2009 22:19, Christian Loitsch wrote:
> Hello
> 
> (please CC me directly)
> 
> i don't need this touchscreen any longer, and would like to donate it to 
> anybody willing to work on improved support.
> 
> 10" (currently used with an MSI Wind)
> 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
> (you can find this touchscreen on ebay)
> 
> I once was able to make the touchscreen work, but it wasn't as easy as 
> pluging the touchscreen in.
> 
> First come first served, except for Daniel Ritz (the developer of the 
> touchscreen module), who has highest priority.

thanks a lot for this offer! but i will leave it to other interested
people since i have access to a eGalax screen (from xenarc).

> 
> Please just email me your address.  I will try to update: 
> <http://christian.delta64.com/touchscreen/stillAvailable.html>
> as fast as possible.
> 
> Please give me ~1week to prepare the package (and also give Daniel some 
> time to respond).
> 
> a+
> christian
> 
> here are some details i found out:
> 
> There are currently 3 ways an eGalax touchscreen 0eef:0001 can be 
> handled by the kernel.
> 
> 1) tkusb: a module (GPL) provided by the manufacturer, which is not in 
> the kernel and (AFAIK) requires a binary-only xorg module. [1]
> 
> 2) usbhid: which recognized my touchscreen, but I was not able to make 
> it work in xorg.
> 
> 3) the usbtouchscreen module.  This module only "accepts" the 
> touchscreen if usbhid did not (so I currently unload usbhid before 
> activating the touchscreen).
> This module however only works if the touchscreen is set to use a 
> different mode. (loading the tkusb module before the usbtouchscreen 
> module works, as tkusb sends this mode-change command to the touchscreen 
> [2])
> 
> The touchscreen works perfectly with usbtouchscreen and evdev.  I was 
> not able to make it work in any other way.
> 
> If I understood the usbtouchscreen code correctly you would just need to 
> add a device specific init for eGalax touchscreens and send the command 
> ([2]) to the device.  (AFAIK eeti does the same in their tkusb module 
> for every eGalax touchscreen).
> 
> [1]  <http://home.eeti.com.tw/web20/eGalaxTouchDriver/linuxDriver.htm>
> [2]  code from eeti-driver tkusb.c:
> ---
>                 #ifndef _REMOVE_CHANGE_FORMAT^M
>                         scr->output[0] = 0x0A;^M
>                         scr->output[1] = 1;^M
>                         scr->output[2] = 'A';^M
>                         if( !DoSendData( scr, 3 ) )^M
> ---
jup, that's the way to do it. i have some patches for usbtouchscreen
from various people in the mess that is my mailbox. i think one of
them adds exactly that init code. i'll try to get those in mergable
state soon...

thanks
-daniel




      reply	other threads:[~2009-10-12 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 20:19 eGalax TouchScreen Christian Loitsch
2009-10-12 10:17 ` Daniel Ritz [this message]

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=4AD30229.6090607@gmx.ch \
    --to=daniel.ritz@gmx.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@abc.delta64.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox