From: Philipp Zabel <philipp.zabel@gmail.com>
To: Paul Parsons <lost.distance@yahoo.com>
Cc: Dmitry Artamonow <mad_soft@inbox.ru>,
eric.y.miao@gmail.com, koen@dominion.thruhere.net,
dmitry.torokhov@gmail.com, linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/2] pxa/hx4700: Add Synaptics NavPoint (PXA27x SSP/SPI) driver
Date: Wed, 23 Nov 2011 23:49:01 +0100 [thread overview]
Message-ID: <1322088541.18388.16.camel@flow> (raw)
In-Reply-To: <1322081102.2448.YahooMailClassic@web29004.mail.ird.yahoo.com>
Am Mittwoch, den 23.11.2011, 20:45 +0000 schrieb Paul Parsons:
> --- On Wed, 23/11/11, Dmitry Artamonow <mad_soft@inbox.ru> wrote:
> > BTW, it's funny that driver is placed in input/mouse, but
> > actually
> > reports only keyboard events :)
> > Anyway, reporting coordinates can be added at some later
> > point.
>
> That's right, the underlying hardware is a touchpad so the driver could report mouse events if required. Obviously the hx4700 already has a working touchscreen so it's not obvious what benefit a second mouse device would add. And I'm not aware of any other platforms which use the NavPoint.
I agree, the NavPoint is pretty useless as a touchpad.
I think there's some kind of Logitech Wireless Keyboard / Remote that
has a NavPoint, but I'm not aware of anything with them that would run
linux either.
regards
Philipp
next prev parent reply other threads:[~2011-11-23 22:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 16:45 [PATCH v3 1/2] pxa/hx4700: Add Synaptics NavPoint (PXA27x SSP/SPI) driver Paul Parsons
2011-11-23 19:51 ` Dmitry Artamonow
2011-11-23 20:45 ` Paul Parsons
2011-11-23 22:49 ` Philipp Zabel [this message]
2011-11-23 22:46 ` Philipp Zabel
2011-11-23 23:04 ` Philipp Zabel
2011-11-24 1:06 ` Paul Parsons
2011-11-23 23:01 ` Russell King - ARM Linux
2011-11-24 2:53 ` Paul Parsons
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=1322088541.18388.16.camel@flow \
--to=philipp.zabel@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=koen@dominion.thruhere.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=lost.distance@yahoo.com \
--cc=mad_soft@inbox.ru \
/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).