All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yani Ioannou <yani.ioannou@gmail.com>
To: dtor_core@ameritech.net
Cc: Robert Love <rml@novell.com>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] IBM HDAPS accelerometer driver.
Date: Sun, 28 Aug 2005 07:00:24 -0400	[thread overview]
Message-ID: <25381867050828040065312bf5@mail.gmail.com> (raw)
In-Reply-To: <d120d50005082613122595cde8@mail.gmail.com>

On 8/26/05, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> On 8/26/05, Robert Love <rml@novell.com> wrote:
> > On Fri, 2005-08-26 at 14:27 -0500, Dmitry Torokhov wrote:
> >
> > > What this completion is used for? I don't see any other references to it.
> >
> > It was the start of the release() routine, but I decided to move to
> > platform_device_register_simple() and use its release, instead.  So this
> > is gone now in my tree.
> >
> > > I'd rather you used absolute coordinates and set up
> > > hdaps_idev->absfuzz to do the filtering.
> >
> > Me too.
> >
> 
> Btw, if you set up absolute input device it will be claimed by joydev
> instead of mousedev and will not get in a way of normal operation
> while still available for playing. So you could just kill all that
> enabling/disabling code and have input device always activated.

Even easier - I submitted a patch a while back against the old hdaps
driver (on hdaps-devel) to use the hdaps sensor's keyboard/mouse
activity readings to selectively disable/enable the mouse (and
re-enable it after a time of no keyboard/mouse activity). This makes
the mouse device much more usable, and you don't end up fighting it
while trying to use the normal mouse/keyboard.

Yani

  reply	other threads:[~2005-08-28 11:00 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26 15:18 [patch] IBM HDAPS accelerometer driver Robert Love
2005-08-26 17:05 ` Bill Nottingham
2005-08-26 17:15   ` Robert Love
2005-08-26 17:33 ` Brian Gerst
2005-08-26 17:33   ` Robert Love
2005-08-26 18:01     ` Arjan van de Ven
2005-08-26 18:03       ` Robert Love
2005-08-26 18:45         ` Dave Jones
2005-08-26 18:52           ` Robert Love
2005-08-26 19:55         ` Alan Cox
2005-08-26 19:29           ` Robert Love
2005-08-26 19:33             ` Jeff Garzik
2005-08-26 19:37               ` Robert Love
2005-08-26 20:21                 ` Alan Cox
2005-08-26 22:43                 ` Andi Kleen
2005-08-26 20:27             ` Dave Jones
2005-08-26 19:54   ` Alan Cox
2005-08-26 18:18 ` Andrew Morton
2005-08-26 18:30   ` Robert Love
2005-08-26 19:27 ` Dmitry Torokhov
2005-08-26 19:39   ` Robert Love
2005-08-26 19:43     ` Robert Love
2005-08-26 20:09       ` Dmitry Torokhov
2005-08-26 20:12     ` Dmitry Torokhov
2005-08-28 11:00       ` Yani Ioannou [this message]
2005-08-27 12:41 ` Pavel Machek
2005-08-28  2:59   ` Mikulas Patocka
2005-08-28  8:09     ` Pavel Machek
2005-08-28  9:21       ` Oliver Neukum
2005-08-28 19:30       ` Mikulas Patocka
2005-08-29  8:35         ` Pavel Machek
2005-08-29  8:59           ` Oliver Neukum
2005-08-29  9:10             ` Pavel Machek
2005-08-30 17:44               ` Mikulas Patocka
2005-08-31  0:12                 ` Yani Ioannou
     [not found] <4FOa3-8fm-39@gated-at.bofh.it>
     [not found] ` <4GlyV-3Rk-3@gated-at.bofh.it>
     [not found]   ` <4GqyE-2bk-19@gated-at.bofh.it>
     [not found]     ` <4GrEp-3E2-21@gated-at.bofh.it>
2005-08-28 16:26       ` Robert Hancock

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=25381867050828040065312bf5@mail.gmail.com \
    --to=yani.ioannou@gmail.com \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.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.