mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shaun Jackman <sjackman@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] liyitec: Liyitec PS/2 touchscreen driver
Date: Thu, 2 Feb 2006 16:54:52 -0700	[thread overview]
Message-ID: <7f45d9390602021554gcb602a1i3fd7378942601c65@mail.gmail.com> (raw)
In-Reply-To: <d120d5000602021512x42be2006h31e63cb6d78ac1b3@mail.gmail.com>

On 2/2/06, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> On 2/2/06, Shaun Jackman <sjackman@gmail.com> wrote:
> > [PATCH] liyitec: Liyitec PS/2 touchscreen driver
> >
> > Add an input driver for the Liyitec PS/2 touchscreen.
>
> I don't see any suibstantial differences from the older patch. I think
> it should be integrated into psmouse. Is there a way to query the
> device? What kind of boxes use this touchscreen? Maybe using DMI is an
> option, like lifebook does?

I supplied some commentary in another email. I wasn't entirely sure
how to separate some free commentary from the ChangeLog entry in a
[PATCH] post. Sorry for the confusion.

The system I have, an Advantech touchscreen computer, has no DMI
information. So that option is out, at least in my case.

# ./dmidecode
# dmidecode 2.7
# No SMBIOS nor DMI entry point found, sorry.

I agree this driver would be best as a psmouse drive, but some
reliable detection code is necessary first. The serio driver does work
as is. If the user loads the liyitec.ko module or compiles the driver
into the kernel, she likely knows what she's doing.

I suspect there exists a detection routine using PS/2 commands that
will work, but I haven't figured one out yet.

Cheers,
Shaun

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02 23:02 Shaun Jackman
2006-02-02 23:12 ` Dmitry Torokhov
2006-02-02 23:54   ` Shaun Jackman [this message]
2006-02-04  0:39   ` Shaun Jackman
2006-02-04  7:05     ` Vojtech Pavlik
2006-02-04 18:32       ` Shaun Jackman

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=7f45d9390602021554gcb602a1i3fd7378942601c65@mail.gmail.com \
    --to=sjackman@gmail.com \
    --cc=dmitry.torokhov@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®