linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@mail.ru>
To: Richard Atterer <atterer@debian.org>
Cc: linux-kernel@vger.kernel.org, vojtech@ucw.cz,
	linux-input@vger.kernel.org, rubini@ipvvis.unipv.it,
	jkosina@suse.cz
Subject: Re: [PATCH 2.6.28] mousedev: Allow devices to be excluded from /dev/input/mice
Date: Fri, 30 Jan 2009 20:29:59 -0800	[thread overview]
Message-ID: <20090131042959.GA3529@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <20090130120456.GA20461@arbonne.lan>

Hi Richard,

On Friday 30 January 2009 04:04:56 Richard Atterer wrote:
> From: Richard Atterer <atterer@debian.org>
>
> Allow devices to be excluded from /dev/input/mice
>
> This patch adds an "ignoreid=0x1234:0x5678" parameter to the mousedev
> module. If a mouse matches the given device ID(s), its movement and button
> presses will not be relayed via /dev/input/mice.
>

Thank you for the patch, however I don't think that it is the right solution.

> Why is this needed? In my case, I'm using some mice as sensors (robotic
> application, more or less), so their movement should not influence the
> mouse pointer at all.

I think this is the case where EVIOCGRAB use is warranted then.

> I could simply specify only my main mouse in
> xorg.conf rather than /dev/input/mice. However, /dev/input/mice is the only
> way to allow hot-plugging of mice with X.
>

The newer X does support input hotplug pretty well actually.

> This feature could also be used to disable non-working/buggy touchpads in
> laptops.
>

You can already do that by unbinding serio and usb devices from their 
respective drivers, no need to modify mousedev.

-- 
Dmitry

  reply	other threads:[~2009-01-31  4:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 12:04 [PATCH 2.6.28] mousedev: Allow devices to be excluded from /dev/input/mice Richard Atterer
2009-01-31  4:29 ` Dmitry Torokhov [this message]
2009-01-31 19:17   ` Richard Atterer

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=20090131042959.GA3529@dtor-d630.eng.vmware.com \
    --to=dtor@mail.ru \
    --cc=atterer@debian.org \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rubini@ipvvis.unipv.it \
    --cc=vojtech@ucw.cz \
    /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).