From: Vojtech Pavlik <vojtech@suse.cz>
To: Shaun Jackman <sjackman@gmail.com>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] liyitec: Liyitec PS/2 touchscreen driver
Date: Sat, 4 Feb 2006 08:05:20 +0100 [thread overview]
Message-ID: <20060204070519.GA5866@suse.cz> (raw)
In-Reply-To: <7f45d9390602031639k3c5ae010gbd52a8fdd8bb863b@mail.gmail.com>
On Fri, Feb 03, 2006 at 05:39:30PM -0700, Shaun Jackman wrote:
> So, finally, assuming there is no way to detect the touch panel's
> presence, should the driver still be rolled into psmouse? If so, how
> should the user specify she wishes to use the liyitec driver, and
> which serio (PS/2) port the liyitec touch screen is on?
>
> My current patch implements the Liyitec driver as a serio driver that
> grabs every available PS/2 port. Quite unfriendly, but works in the
> typical case where the keyboard driver grabs the first port, and the
> Liyitec driver grabs the psaux port.
I hope the driver at least checks that the port is untranslated
(SERIO_I8042, not SERIO_I8042_XL), and that the device behaves as a
mouse.
Btw, I assume the packet format is also indistinguishable from a
standard PS/2 mouse?
If it were integrated into psmouse, it probably need to be enabled by a
module parameter.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2006-02-04 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 23:02 [PATCH] liyitec: Liyitec PS/2 touchscreen driver Shaun Jackman
2006-02-02 23:12 ` Dmitry Torokhov
2006-02-02 23:54 ` Shaun Jackman
2006-02-04 0:39 ` Shaun Jackman
2006-02-04 7:05 ` Vojtech Pavlik [this message]
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=20060204070519.GA5866@suse.cz \
--to=vojtech@suse.cz \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sjackman@gmail.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 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.