Re: [PATCH] Wireless Security Lock driver.

>>>>> "Pavel" == Pavel Machek <[email protected]> writes:

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?

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.

-JimC
-- 
James H. Cloos, Jr. <[email protected]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] Wireless Security Lock driver.
  - From: Pavel Machek <[email protected]>

References:
- [PATCH] Wireless Security Lock driver.
  - From: Brian Schau <[email protected]>
- Re: [PATCH] Wireless Security Lock driver.
  - From: Pavel Machek <[email protected]>
- Re: [PATCH] Wireless Security Lock driver.
  - From: Brian Schau <[email protected]>
- Re: [PATCH] Wireless Security Lock driver.
  - From: Pavel Machek <[email protected]>

Prev by Date: busy usenet server: only stable kernel is 2.6.12-mm1, rest (including 2.6.13-rc4*) barfs within a few days
Next by Date: Re: [ACPI] [GIT PATCH] ACPI patches for 2.6.13
Previous by thread: Re: [PATCH] Wireless Security Lock driver.
Next by thread: Re: [PATCH] Wireless Security Lock driver.
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind]