<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/hid/hid-speedlink.c, branch linux-3.4.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.4.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.4.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2013-09-27T00:15:34Z</updated>
<entry>
<title>HID: Fix Speedlink VAD Cezanne support for some devices</title>
<updated>2013-09-27T00:15:34Z</updated>
<author>
<name>Stefan Kriwanek</name>
</author>
<published>2013-08-25T08:46:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=355c557b3e0164eaf75aded30e92da5a3a818c5f'/>
<id>urn:sha1:355c557b3e0164eaf75aded30e92da5a3a818c5f</id>
<content type='text'>
commit 06bb5219118fb098f4b0c7dcb484b28a52bf1c14 upstream.

Some devices of the "Speedlink VAD Cezanne" model need more aggressive fixing
than already done.

I made sure through testing that this patch would not interfere with the proper
working of a device that is bug-free. (The driver drops EV_REL events with
abs(val) &gt;= 256, which are not achievable even on the highest laser resolution
hardware setting.)

Signed-off-by: Stefan Kriwanek &lt;mail@stefankriwanek.de&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>HID: Add driver to fix Speedlink VAD Cezanne support</title>
<updated>2011-06-08T07:45:37Z</updated>
<author>
<name>Stefan Kriwanek</name>
</author>
<published>2011-05-27T16:40:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=74bc6953135ae1478acc18046321bfca05b0e823'/>
<id>urn:sha1:74bc6953135ae1478acc18046321bfca05b0e823</id>
<content type='text'>
Speedlink VAD Cezanne have a hardware bug that makes the cursor "jump" from one
place to another every now and then. The issue are relative motion events
erroneously reported by the device, each having a distance value of +256. This
256 can in fact never occur due to real motion, therefore those events can
safely be ignored.  The driver also drops useless EV_REL events with a value of
0, that the device sends every time it sends an "real" EV_REL or EV_KEY event.

Signed-off-by: Stefan Kriwanek &lt;mail@stefankriwanek.de&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
</feed>
