-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Andy Green wrote: |> Somebody in the thread at some point said: |> | I often get the X argument to the accelerometer stuck between 0x6a0 and |> | 0x8ee. |> | |> | It seems like it might be related to suspend/resume. |> | |> | This is with andy git pulled on Friday. |> |> Guh. |> |> Which accelerometer is it that does this? Do you have both top and |> bottom accelerometer /dev/input/event open at this time? Does it still |> happen if you have only one open? | It happens with both accelerometers. They seem to be in sync - I open | them both. I have to do more testing. Sometimes I only see input3 and | not the other (I think it i s input2). |> "Related to suspend/resume" means that it is OK, you suspend/resume and |> then it is immediately broken? | This is probably premature. I just saw it and I'm pretty sure a | suspend/resume didn't happen since startup. I have a very complicated | application, so it will take time to isolate.
I very recently worked on this, if you're not sure it was Friday you last pulled confirm that arch/arm/mach-s3c2440/mach-gta02.c has this in http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=650b7e2598341281ace453deda29c7de075a4512 - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkgv6m4ACgkQOjLpvpq7dMpkEQCghwIn+mmmEdwxvdYE77+XJxit 2esAn2lJ4cm1/p/8MWAbtfyY/XBmGgjF =zPjN -----END PGP SIGNATURE-----
