From: Pavel Machek <pavel@ucw.cz>
To: Brian Schau <brian@schau.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Wireless Security Lock driver.
Date: Sat, 30 Jul 2005 22:31:59 +0200 [thread overview]
Message-ID: <20050730203159.GB9418@elf.ucw.cz> (raw)
In-Reply-To: <42EBDEA9.60505@schau.com>
Hi!
> Hehe - the WSLs are already reality. Sitecom is a producer of
> these and you can get another brand from ThinkGeek.
Aha, ok.
> Sitecom device:
> http://www.sitecom.com/products_info.php?product_id=293&grp_id=1
>
> ThinkGeek:
> http://www.thinkgeek.com/gadgets/security/698d/
>
> Why in kernel? Well, the device is based on the Cypress Ultra
> Mouse. So with a non WSL aware kernel the events from the WSL
> will be merged into the standard mouse input queue which will
> make your mouse pointer move uncontrollable - it'll jump across
> the screen in a couple of steps every 3 seconds or so.
> Quite amusing but not very handy!
Well, that is if you use /dev/psaux, right? Using event devices you
should be able to access it from userland. Or you could drive it using
libusb driver.
Pavel
--
if you have sharp zaurus hardware you don't need... you know my address
next prev parent reply other threads:[~2005-07-30 20:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 14:51 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 [this message]
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
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=20050730203159.GB9418@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=brian@schau.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®