Iain B. Findleton wrote:
Michael 'Mickey' Lauer wrote:
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
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 git.openmoko.org it appears to me that this
should not be true, and if I recall correctly, proper output was couming
out under
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 git.openmoko.org it appears to me that this
should not be
Michael 'Mickey' Lauer wrote:
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 git.openmoko.org it
On Thu, 17 Dec 2009 12:32:46 -0500
Iain B. Findleton ifindle...@videotron.ca wrote:
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.
I
5 matches
Mail list logo