Messages in this thread | | | Date | Sun, 31 Jul 2005 16:08:40 +0200 | From | Pavel Machek <> | Subject | Re: [PATCH] Wireless Security Lock driver. |
| |
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 :-). > > There's a script to this on the gentoo wiki via BlueZ. > > http://gentoo-wiki.com/TIP_Bluetooth_Proximity_Monitor > > I personally think the problem with this approach is that most phones have > bluetooth enabled explicitly as an option, it doesn't run all the time, or > default on. Primarily this is because bluetooth can drain your phone's > battery (though, I don't know by how much, if you're not actually > transferring data over it).
I have bluetooth turned on all the time, anyway, and it does not drain battery that badly (standby time goes down 30%?).
> A CR2032 cell, in a specific piece of kit, is going to last for a lot longer > than a phone battery.
Well, you know... phones have *rechargable* batteries :-).
-- 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |