linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Alex Hudson <home@alexhudson.com>
Cc: Linux Input <linux-input@vger.kernel.org>
Subject: Re: Driver problems: t213 on i8042 port
Date: Wed, 15 Dec 2010 00:03:52 -0800	[thread overview]
Message-ID: <20101215080352.GA11920@core.coreip.homeip.net> (raw)
In-Reply-To: <1292235175.2805.19.camel@lapland.localdomain>

On Mon, Dec 13, 2010 at 10:12:54AM +0000, Alex Hudson wrote:
> On Mon, 2010-12-13 at 01:10 -0800, Dmitry Torokhov wrote:
> > > [re: xf86 driver for t213 device]
> >
> > Any chance you could post a link to the sources?
> 
> I can:
> 
> http://www.tabletkiosk.de/files//linux-general/drivers/testing/touchkit-linux-2.2.0.tar.bz2
> 
> There is a thread about this driver on their site as well:
> 
> http://www.tabletkiosk.com/forum/forum_posts.asp?TID=103
> 
> It doesn't compile at all against current X.org; I can send you my diff
> for that but it's all X.org ABI stuff - nothing to do with the actual
> t213 protocol. However, some of this might be moot anyway:
> 
> > You can't simply allowing binding to SERIO_8042 as it will cause
> > touchkit213 to fight with the standard psmouse driver. What needs to be
> > done is to write a sub-driver (or protocol driver) for psmouse module
> > which would probe the devices and automatically select proper protocol.
> > 
> > Please take a look at drivers/input/mouse/psmouse-base.c and friends
> > there.
> 
> Ah, ok, that makes sense then - originally when I was trying to make
> sense of this hardware it kept coming through as a PS/2 mouse but of
> course X.org went slightly nuts with that configuration. 
> 
> As an aside, I wonder if this speaks to some of the problems I was
> having with the X.org driver. I was simply attaching serio_raw to serio4
> as per the instructions; however, if this "fights" (as you describe it)
> with the ps2 mouse, that could explain why it would mostly work but then
> go weird.
> 
> I had a look at psmouse-base.c, and I can see what you mean: also,
> there's a "Touchkit" driver for eGalax, and the protocol there looks
> identical. Weirdly, this isn't working - even though looking at the code
> the detect() function doesn't seem to need a manual trigger.
>

Touchkit initialization sequence looks similar to the one used in X
driver. You probably want to boot with i8042.debug (or activate it via
/sys/module/i8042/parameters/debug), load psmouse module and see what
kind of response you are getting from the device.

Also, have you tried forcing touchkit protocol by doing:

	echo "touchkit" > /sys/bus/serio/devices/serioX/protocol

Thanks.

-- 
Dmitry

      reply	other threads:[~2010-12-15  8:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 10:33 Driver problems: t213 on i8042 port Alex Hudson
2010-12-11  7:15 ` Dmitry Torokhov
2010-12-11  8:56   ` Alex Hudson
2010-12-13  9:10     ` Dmitry Torokhov
2010-12-13 10:12       ` Alex Hudson
2010-12-15  8:03         ` Dmitry Torokhov [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=20101215080352.GA11920@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=home@alexhudson.com \
    --cc=linux-input@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).