Re: [PATCH] Wireless Security Lock driver.

Hi!

> I (and others) have tried using combinations of libusb/userland
> stuff - but have failed miserably.

You may need to patch input to keep hands off that device, but the
rest should be doable using libusb, right? Or talk to vojtech, using
input devices should devices without libusb should be possible too. 

								Pavel
-- 
if you have sharp zaurus hardware you don't need... you know my address
-
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: Brian Schau <[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]>
  • Re: [PATCH] Wireless Security Lock driver.
    • From: Brian Schau <[email protected]>

• Prev by Date: Re: revert yenta free_irq on suspend
• Next by Date: Re: [ANNOUNCE 0/7] Open-iSCSI/Linux-iSCSI-5 High-Performance Initiator
• 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]