Accelerometers in Kernel 2.6.28-rc4

[Simon Kagstrom]

On Sat, 24 Jan 2009 17:21:09 +0100
Michael Tansella <michael-tansella at gmx.de> wrote:

> I made a mistake. I do not really get two different values I get
> twice the same (3D) value but a different timestamp (see below). But
> anyway this is not correct. I don't want to set a threshold, because
> I need every value with an equidistant timestamp.

Well, it was more to see if the behavior changes with the threshold,
but anyway:

> Any idea what's going wrong?

Looking at

  http://wiki.openmoko.org/wiki/Accelerometer_data_retrieval#Data_acquisition

are you sure this isn't just the synchronization events?

   |----- time ------|  |type| |code|  |-value-|
   8c66 4819 721c 0006   0002   0002   03a8 0000
   8c66 4819 7222 0006   0000   0000   0000 0000   <--- Time looks quite close to the last non-sync events
   8c66 4819 99e6 0006   0002   0000   0048 0000   <--- Larger time distance and real data
   8c66 4819 9a36 0006   0002   0001   0024 0000
   8c66 4819 9a50 0006   0002   0002   0396 0000
   8c66 4819 9a57 0006   0000   0000   0000 0000   <--- Another sync message, small time distance

I'm no expert on the data format though.

// Simon