lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090109101317.GC3396@elf.ucw.cz>
Date:	Fri, 9 Jan 2009 11:13:17 +0100
From:	Pavel Machek <pavel@...e.cz>
To:	Éric Piel <eric.piel@...mplin-utc.net>
Cc:	kernel list <linux-kernel@...r.kernel.org>, trenn@...e.de,
	hmh@....eng.br
Subject: Re: HP accelerometer: free fall detection working, testers wanted

On Sun 2008-11-30 23:16:29, Éric Piel wrote:
> Pavel Machek schreef:
> > Hi!
> > 
> >>> I got free fall detection to work -- apparently BIOS does all the
> >>> important stuff itself. 
> >>>
> >>> Now... I'd like some testers. (Don't comment on code... yet. Yes, it
> >>> has some issues).
> 
> >> Also, how do you try free fall? Did you try also with the lid
> >> opened?
> > 
> > With the lid opened, too, yes. I just took the machine, then tried to
> > let go and catch it meter below that. (Of course I did not really let
> > go, but released the grip and followed...)
> 
> Hi,
> I've tested it. Mostly, it works. If I let it fall, it detects it. If I
> repeat, it detects it again. If shake it, it doesn't detect any freefall
> (good). However, for this to work on my laptop (2510p), after the device
> is turned on, the AC must be unplugged and lid closed before it starts
> working. It seems that that's only this specific state that triggers the
> configuration of the sensor by the bios. Once setup, I can plug back and
> open again the lid, the sensor keeps detecting the freefalls (until it's
> turned off again).
> 
> So I think it's still necessary to explicitly set up the sensor. It's
> just a matter of setting up the registers as the bios does. We should be
> able to manage (just by dumping them once).

Well, according to HP we should not be setting registers
ourselves. Maybe CLRI method needs to be called or something?

> BTW, there were a couple of problems with the scripts. You have change
> "/dev/misc" to "/dev/freefall" (which I also like more) but forgot to
> update the driver itself.
> 
> For hp3dg, it couldn't find the led (not the same truncation of the name
> of the led). Probably you could replace the name of the led by:
> /sys/class/leds/*hddprotect*/

Yes, the scripts were very very quick hacks.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ