mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shaun Jackman <sjackman@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Liyitec PS/2 touch panel driver [PATCH]
Date: Thu, 2 Feb 2006 16:11:05 -0700	[thread overview]
Message-ID: <7f45d9390602021511t108b4931kd17d3bca5eb0d5cd@mail.gmail.com> (raw)
In-Reply-To: <200601312320.05143.dtor_core@ameritech.net>

On 1/31/06, Dmitry Torokhov <dtor_core@ameritech.net> wrote:
> What stops this driver form binding to serio ports that have devices other
> that Liyitec touchscreen connected to them? Such as keyboard port when
> keyboard works in non-translated mode or regular AUX port with standard
> PS/2 mouse? Is there a way to query for presence of the touchscreen?
>
> Moreover this driver should be integrated into psmouse so proper protocol
> is selected automatically.

I've just posted an updated version of my Liyitec driver that
incorporates the trivial changes suggested by others on this list.
This driver is quite useful in its current state, as it does allow a
Liyitec touch screen to be used, which currently has no support at
all. It does however have a few outstanding issues.

1. The Liyitec driver will grab all unclaimed PS/2 devices.
2. It does this because there is no probing and identification code.
3. This driver would probably be better off as a psmouse driver rather
than a serio driver, but this would first require the missing probe
code.

It should certainly be possible to detect the presence of a Liyitec
touch screen, but I haven't figured out how yet. Trivially, the
Liyitec touch screen appears to be a PS/2 mouse that happens to be
returning very unusual coordinates.

Cheers,
Shaun

      parent reply	other threads:[~2006-02-02 23:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 22:59 Shaun Jackman
2006-02-01  0:22 ` Alexey Dobriyan
2006-02-02  0:50   ` Shaun Jackman
2006-02-01  1:03 ` Jiri Slaby
2006-02-02  0:52   ` Shaun Jackman
2006-02-01  4:20 ` Dmitry Torokhov
2006-02-02  1:00   ` Shaun Jackman
2006-02-02 23:11   ` Shaun Jackman [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=7f45d9390602021511t108b4931kd17d3bca5eb0d5cd@mail.gmail.com \
    --to=sjackman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®