public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Schau <brian@schau.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: James Cloos <cloos@jhcloos.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Wireless Security Lock driver.
Date: Sun, 31 Jul 2005 14:43:29 +0200	[thread overview]
Message-ID: <42ECC771.2050607@schau.com> (raw)
In-Reply-To: <20050731095207.GJ9418@elf.ucw.cz>

Yes, the quirk is in the patch :-)

Pavel Machek wrote:
> Hi!
> 
> 
>>Pavel> Well, that is if you use /dev/psaux, right? Using event devices
>>Pavel> you should be able to access it from userland.
>>
>>Would /dev/input/mice not also be affected?
> 
> 
> Yes, /dev/input/mice == /dev/psaux.
> 
> 
>>Until X can hotplug input devices /dev/input/mice rather than evdev
>>will remain necessary in many cases for a reasonable user experience.
>>
>>So at least a quirk/whatever to keep that device from being included
>>in mice (and psaux) should be added.
> 
> 
> Yes... why not. But that should be close to one liner, right?
> 								Pavel

  reply	other threads:[~2005-07-31 12:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-30 14:51 [PATCH] Wireless Security Lock driver Brian Schau
2005-07-30 15:01 ` Michael Krufky
2005-07-30 15:16   ` Brian Schau
2005-07-30 15:57     ` Zwane Mwaikambo
2005-07-30 16:02       ` Brian Schau
2005-07-30 17:11         ` Michael Krufky
2005-07-30 18:05           ` Brian Schau
2005-07-30 19:42 ` Pavel Machek
2005-07-30 20:10   ` Brian Schau
2005-07-30 20:31     ` Pavel Machek
2005-07-30 21:14       ` Brian Schau
2005-07-30 21:16         ` Pavel Machek
2005-07-30 22:06           ` Brian Schau
2005-07-31  8:42       ` James Cloos
2005-07-31  9:52         ` Pavel Machek
2005-07-31 12:43           ` Brian Schau [this message]
2005-07-31 16:14           ` James Cloos
2005-07-31 13:59   ` Alistair John Strachan
2005-07-31 14:08     ` Pavel Machek

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=42ECC771.2050607@schau.com \
    --to=brian@schau.com \
    --cc=cloos@jhcloos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@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