From: Brian Schau <brian@schau.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Wireless Security Lock driver.
Date: Sat, 30 Jul 2005 22:10:17 +0200 [thread overview]
Message-ID: <42EBDEA9.60505@schau.com> (raw)
In-Reply-To: <20050730194215.GA9188@elf.ucw.cz>
Hi Pavel,
Hehe - the WSLs are already reality. Sitecom is a producer of
these and you can get another brand from ThinkGeek.
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!
The problem is described here:
http://www.qbik.ch/usb/devices/showdev.php?id=3095
The WSL kernel driver will translate the device packets to a
separate event queue.
And you're right. The WSL driver is not a standalone thingy -
you'll some userland tools as well. These can be gotten from:
http://www.schau.com/l/wsl/index.html
The tools contains a patch for xscreensaver (patch submitted to
maintainer) and a small WSL monitor program which will monitor
in-range/out-of-range signals and disable/enable xscreensaver
as needed.
/brian
Pavel Machek wrote:
> Hi!
>
>
>>I've attached a gzipped version of my Wireless Security Lock patch
>>for v2.6.13-rc4.
>>A Wireless Security Lock (WSL or weasel :-) is made up of two parts.
>>One part is a receiver which you plug into any available USB port.
>>The other part is a transmitter which at fixed intervals sends
>>"ping packets".
>>A "ping packet" usually consists of an ID and a flag telling if the
>>transmitter has just been turned on.
>
>
> Idea is good... but why don't you simply use bluetooth (built into
> many notebooks) and bluetooth-enabled phone?
>
> Probably could be done in userspace, too :-).
> Pavel
>
next prev parent reply other threads:[~2005-07-30 20:13 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 [this message]
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
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=42EBDEA9.60505@schau.com \
--to=brian@schau.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