On Wed, May 12, 2010 at 01:48:32PM -, Marcin Juszkiewicz wrote:
I backported 4 patches from mainline kernel (2.6.34-rc7) and resulting
modprobe psmouse force_elantech=1 works on my laptop.
The patches are already part of 2.6.34-rc7.
What isn't in yet is the autodetection, so you actually
On Thu, Apr 29, 2010 at 09:54:08PM -, Dmitry Torokhov wrote:
I am guessing you are looking into something similar to ALPS driver
options but I am not sure if this is really needed.
Actually I wasn't aware of the internals of the ALPS driver, or the
existance of an ALPS driver, for that
On Thu, Apr 29, 2010 at 08:35:15PM -, viking wrote:
I applied Florian's suggestion in comment 43, and it worked. Cheers!
Excellent. I'll submit another patch making sure the driver assumes the
right hardware version for your device to linux-input shortly.
--
BOFH excuse #221:
The
On Thu, Apr 29, 2010 at 08:55:05PM -, Dmitry Torokhov wrote:
Hmm, I wonder if all firmwares with major 2 and above produce 6-byte
protocol and the entire jumpy cursor workaround for firmware 2.34 is
not really needed.
I'm fairly sure that'd be wrong. The jumpy_cursor codepath very much
For everyone for which the original set of 4 patches worked: there's
good news. They'll probably be in 2.6.34 once it comes out, or at least
in 2.6.35. http://www.spinics.net/lists/linux-input/msg08298.html
On Tue, Apr 27, 2010 at 09:53:11PM -, Tyson Williams wrote:
Yes, one and two figure
On Tue, Apr 27, 2010 at 06:50:05PM -, Tyson Williams wrote:
Now I can say that this patch didn't work for me. Using the patched
module, my touchpad has no predictable behavior. If I try to move the
mouse or click, maybe nothing will happen...or maybe the mouse will jump
wildly around the
On Mon, Apr 26, 2010 at 11:00:51PM -, Tyson Williams wrote:
Florian's original 4 patches did not work for me. When I tried to modprobe
the patched module, it failed because of an invalid format:
FATAL: Error inserting psmouse
You're correct, the first two bits of the first byte indeed indicates
the number of fingers used currently, just like with any other version
of the firmware using 6 byte packets. The x- and y-coordinates are also
identical to what earlier firmware versions provided, with one minor
difference: the
I fixed the driver to work on newer touchpad firmwares, and sent off the
patches to the linux-input mailinglist: http://www.spinics.net/lists
/linux-input/msg08277.html
These patches make things Just Work on my ASUS UL30A, but I've pretty
much hardcoded my particular firmware version to avoid
On Sun, Apr 25, 2010 at 01:13:33PM -, ALLurGroceries wrote:
Wow, nice timing. I had just finished a patch but before I could clean
it up you had already posted your (much better) patch set.
Hah! Sorry, mate :)
For reference, I attached my quick-and-dirty patch that works on the
ASUS
On Sun, Apr 25, 2010 at 02:42:50PM -, ALLurGroceries wrote:
I could be wrong about 0x0c to reg_10 with regard to your patches.
Instead of disregarding the high bits I copied the code from the two
finger condition (but using normal resolution) which is a bit different,
and probably isn't
*** This bug is a duplicate of bug 512192 ***
https://bugs.launchpad.net/bugs/512192
** This bug has been marked a duplicate of bug 512192
Can't configure Elan tech touchpad on Dell Inspiron 11z, Asus K7I0C and
maybe also Dell Mini 10 (not V), ASUS k40in, Asus U81A and ASUS UL80-VT.
--
12 matches
Mail list logo
