Re: [PATCH] Wireless Security Lock driver.

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

-
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/

---

• 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]>
  • Re: [PATCH] Wireless Security Lock driver.
    • From: James Cloos <[email protected]>
  • Re: [PATCH] Wireless Security Lock driver.
    • From: Pavel Machek <[email protected]>

• Prev by Date: Re: 2.6.13-rc4-mm1
• Next by Date: Re: [2.6.13-rc4] Bug in the wireless code?
• 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]