Fwd: freerunner accelerometers
andy at openmoko.com
Sun Sep 21 18:00:19 CEST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Somebody in the thread at some point said:
| I posted this before, but got no replies.
| I wrote myself a little app that reads out the accelerometers.
| This works perfectly for /dev/input3 returning reasonable
| values. ( written a spirit level style app )
| The second(first) device does not produce any data.
| After the freenunner has gone to sleep once
| one axis further on produces values with a large offset,
| going over range in a 90 segment of rotation
| i.e. the output value is stuck at max.
| To remove the error the freerunner has to be powered down.
| Any ideas?
There's a bunch of stuff on accellerometers from Sean McNeil coming soon
into 2.6.26 branch, not sure if it will cover the offset business but it
should cover the "no data" thing.
Is there any sign in dmesg about "device BOOT reload failed" after resume?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the hardware