From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: William Manson <WManson@synaptics.com>
Cc: Christopher Heiny <Cheiny@synaptics.com>,
Allie Xiong <axiong@synaptics.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH 1/1] input/touchscreen: Synaptics Touchscreen Driver
Date: Tue, 5 Jan 2010 14:40:52 -0800 [thread overview]
Message-ID: <20100105224051.GA7869@core.coreip.homeip.net> (raw)
In-Reply-To: <7B4B50AC280A5E45A42CD2D364A3CE2F2733F75A3E@USW-EX2K7-1.synaptics-inc.local>
On Tue, Jan 05, 2010 at 01:57:37PM -0800, William Manson wrote:
> Hi Dmitry -
>
> Yes - we are planning on extending support for our new touchpads. As
> far as I know there is a Linux PS/2 driver in the works but I don't
> work with that group so I don't know anything about timeframes.
Is there a way to get in touch with that group? As you may know we have
a pretty stable and reliable version of a driver for your older PS/2
products (thanks to Synaptics releasing very detailed interfacing guide)
which is integrated in both kernel and Xorg, and which is used by most
distributions. Users also expect "synaptics" to just work with their
touchpads. I would rather see patches extending the exsting driver
instead of completely new piece of software.
> I also
> don't know if it will be made open source or as a proprietary binary -
> or both. But we are definitely planning on supporting our PS/2
> touchpads on Linux.
>
> I will check into the Interfacing Guide and get back to you. The
> latest is on our web site
> (http://www.synaptics.com/developers/manuals) but it doesn't have info
> about multitouch in it. If there is a newer one I'll let you know.
>
Thank you, much appreciated.
--
Dmitry
next prev parent reply other threads:[~2010-01-05 22:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 20:44 [RFC] [PATCH 0/1] input/touchscreen: Synaptics Touchscreen Driver Christopher Heiny
2009-12-19 20:49 ` [RFC] [PATCH 1/1] " Christopher Heiny
2009-12-20 3:05 ` Dmitry Torokhov
2010-01-03 19:48 ` William Manson
2010-01-03 22:30 ` Dmitry Torokhov
2010-01-05 21:57 ` William Manson
2010-01-05 22:40 ` Dmitry Torokhov [this message]
2010-01-06 0:45 ` William Manson
-- strict thread matches above, loose matches on Subject: below --
2010-02-02 2:03 [RFC PATCH 0/1] " Christopher Heiny
2010-02-02 2:03 ` [RFC PATCH 1/1] " Christopher Heiny
2010-02-17 22:37 [RFC PATCH 0/1] " Christopher Heiny
2010-02-17 22:37 ` [RFC PATCH 1/1] " Christopher Heiny
2010-03-02 9:12 ` Dmitry Torokhov
2010-03-05 1:16 ` Christopher Heiny
2010-03-08 8:36 ` Dmitry Torokhov
2010-03-23 2:07 [RFC PATCH 0/1] " Christopher Heiny
2010-03-23 2:07 ` [RFC PATCH 1/1] " Christopher Heiny
2010-04-02 12:50 ` Jean Delvare
2010-04-02 12:50 ` Jean Delvare
2010-04-05 23:04 ` Christopher Heiny
2010-05-29 0:29 [RFC PATCH 0/1] " Christopher Heiny
2010-05-29 0:29 ` [RFC PATCH 1/1] " Christopher Heiny
2010-05-29 12:32 ` Jean Delvare
2010-05-29 12:32 ` Jean Delvare
2010-05-29 20:34 ` Henrik Rydberg
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=20100105224051.GA7869@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=Cheiny@synaptics.com \
--cc=WManson@synaptics.com \
--cc=axiong@synaptics.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 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.