linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andres Salomon <dilinger@queued.net>
Cc: linux-input@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] OLPC: psmouse: touchpad driver
Date: Fri, 1 Aug 2008 14:34:51 -0400	[thread overview]
Message-ID: <20080801143150.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <20080801142004.2d3d1349@fred>

On Fri, Aug 01, 2008 at 02:20:04PM -0400, Andres Salomon wrote:
> 
> This adds support for OLPC's touchpad.  It has lots of neat features,
> none of which are enabled because the hardware is too buggy.  Instead,
> we use it like a normal touchpad, but with a number of workarounds in
> place to deal with the frequent hardware spasms.  Humidity changes,
> sweat, tinfoil underwear, plugging in AC, drinks, evil felines.. All
> tend to cause the touchpad to freak out.
> 
> Stuff like this keeps me from getting bored.
> 

Good stuff, thank you. I bet you named the module olpc and gave pregix
hgpk to all the functions to mess with mt feeble brain ;) Maybe we
should rename the module to hgpk as well?

> From psmouse-base, we use psmouse_set_state quite a bit, as well
> as piggy-backing off of kpsmoused_wq; so, this also makes those
> available to protocol extensions.
>

Do you think we should provide assessor functions to deal with
kpsmoused instead of playing with it directly? I was thinking about
starting it on-demand for protocols that may use it and shut it off by
default.

-- 
Dmitry

  reply	other threads:[~2008-08-01 18:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 18:20 [PATCH] OLPC: psmouse: touchpad driver Andres Salomon
2008-08-01 18:34 ` Dmitry Torokhov [this message]
2008-08-01 21:15   ` Andres Salomon

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=20080801143150.ZZRA012@mailhub.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dilinger@queued.net \
    --cc=linux-input@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).