SHR-U Accelerometer data

Michael 'Mickey' Lauer mickey at
Thu Dec 17 18:11:51 CET 2009

Am Donnerstag, den 17.12.2009, 11:59 -0500 schrieb Iain B. Findleton:
> Many tests appear to indicate that a complete report set read from
> /dev/input/event2 or event3 is a relative rarity. Looking at the code
> from the lis302dl driver in it appears to me that this
> should not be true, and if I recall correctly, proper output was couming
> out under OM2009.x at one point.

Let me remind you that the driver has changed wrt. RELATIVE and
ABSOLUTE. These days, upon opening the device, only the first report is
a full report. Subsequent reports only contain changed axes.

> Anybody with any thoughts on this issue? According to what I read,
> /dev/input/eventx interface should reliably handle every event and make
> it available.
> The other issue is that the first report from the driver following an
> open on the device should be complete and contain the axis calibration
> values. This appears to be not true in that the first report I get is
> often incomplete in that not all axes are supplied.

I can't confirm that. I'm running andy-tracking and when I call hexdump
<inputnode> the first three entries are always axes 0, 1, 2.


More information about the community mailing list