Accelerometers in Kernel 2.6.28-rc4

[Michael Tansella]

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

For me the problem looks like this.

|type| |code|  |-value-|
0006   0000   0000   0000  0000  -> Seperator time 1
0006   0002   0000   0048  0000  -> Value X1
0006   0002   0001   0024  0000  -> Value Y1
0006   0002   0002   0396  0000  -> Value Z1
0006   0000   0000   0000  0000  -> Seperator time 2 (0.2ms higher than time1)
0006   0002   0000   0048  0000  -> Value X2 (the same X1 )
0006   0002   0001   0024  0000  -> Value Y2 (the same Y1 )
0006   0002   0002   0396  0000  -> Value Z2 (the same Z1 )
0006   0000   0000   0000  0000  -> Seperator time 3 (2.5ms higher than time1)
0006   0002   0000   0048  0000  -> Value X3 (new Value)

I modified the python script from
http://wiki.openmoko.org/wiki/Accelerometer_data_retrieval
(see atachment) that it prints the ms. The result is the same.

204.269 -18 90 882                     
204.462 -18 90 882                     
206.635 -18 90 900                     
206.808 -18 90 900                     
209.127 -36 72 918                     
209.318 -36 72 918                     
211.595 -18 90 918                     
211.789 -18 90 918                     
214.056 -18 72 900                     
214.254 -18 72 900    

Anything must have changed in the new Kernel, cause with the old kernel this 
problem doesn't appear.
Is someone else reading out the Accs and does not have this problem?

Greets Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: AccTest.py
Type: text/x-python
Size: 758 bytes
Desc: not available
Url : http://lists.openmoko.org/pipermail/community/attachments/20090125/0f08c5d9/attachment.py