Perhaps it's time to start asking a question that's been bugging me for a
while now. A loong time ago I implemented an early fix from this thread
(patching alps.c and remaking psmouse.ko) that has sort of jury-rigged me
along until now--it works, mostly, I've got vertical scrolling though the
thing is still damn sensitive even with disable-touchpad-while-typing. But
every time I update my ubuntu, it complains that my psmouse.ko is "third
party" and at the least doesn't replace it. My question: At what point will
there be something in the standard update that will be at least as good as
what I've got, and mostly, what will I have to do at that point to have the
update replace my mods?


On Fri, Jan 25, 2013 at 3:59 PM, Emmanuel Thomé
<email address hidden>wrote:

> Hi all,
>
> In reply to #302:
>
> > Where did you get the device names ("Dolphin", "Pinnacle", "Mercury",
> etc.) and how did you figure out the protocols?
>
> Seconded.
>
> > Can people test Kevin's patch?
>
> I tried it on my dell e6230, it works.
>
> Kevin's patch do not properly take into account the fact that the e6230
> has 16 and 12 bits for the MT slots, and not 15 and 11 (this is the
> ALPS_BITMAP_X_BITS and ALPS_BITMAP_Y_BITS setting).
>
> > If it works, then I'll layer the Dell I15R, I17R, 13z on top of it and
> submit a patch to linux-input.
>
> I'm a bit lost here. Has anybody kept track of the different models
> encountered, and on which laptops ? I think that would help a lot (most
> of the info is probably in here, but very poorly organized ; In
> particular it's difficult to keep track of which laptop models, among
> the ones listed, seemingly have different touchpad hardware).
>
> Dave, what's your decision on your ACPI patch ? I haven't understood
> what was the rationale behind using it, as it seemed to me that we had
> enough material to drive our decision by talking to hardware directly.
> If I understand correctly, you are about to forget this patch, is that
> right ?
>
> Merging all existing code (yours, mine, kevin's) is in fact easier than
> the recollection of what happens where, and possibly requesting some
> testing hardware (posters in this thread can be solicited).
>
> Slightly different is the situation for the short v6 init sequence in
> #280, which diverges from the usual pattern, to say the least. Not
> having RESET_BAT and ENABLE in there makes the sequence functionally
> different from what happens with other hardware.
>
> In the ``seemingly different hardware category'', one could be mistaken
> into listing the Dell E6230/E6430. These do have identical hardware,
> except for the absence of the trackstick on the smaller E6230. My
> reverse-engineering work and merge with bgamari's patches show this.
> These are differentiated by querying the 0xc2c8 register, which is not
> queried in Kevin's patch.
>
> Briefly put, I think we should work making all this stuff cleaner.
>
> E.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (290806).
> https://bugs.launchpad.net/bugs/606238
>
> Title:
>   synaptic touchpad not recognized on dell latitude e6510 and others
>
> Status in The Linux Kernel:
>   Fix Released
> Status in “linux” package in Ubuntu:
>   Fix Committed
> Status in “linux” source package in Precise:
>   Fix Released
> Status in “linux” source package in Quantal:
>   In Progress
> Status in “linux” package in Arch Linux:
>   Fix Released
> Status in openSUSE:
>   New
>
> Bug description:
>   It wrongly recognized as PS/2 Generic Mouse. And then scrolling does
>   not work, but tapping does.
>
>   ProblemType: Bug
>   AplayDevices:
>    **** List of PLAYBACK Hardware Devices ****
>    card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
>      Subdevices: 1/1
>      Subdevice #0: subdevice #0
>   Architecture: i386
>   ArecordDevices:
>    **** List of CAPTURE Hardware Devices ****
>    card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
>      Subdevices: 2/2
>      Subdevice #0: subdevice #0
>      Subdevice #1: subdevice #1
>   AudioDevicesInUse:
>    USER        PID ACCESS COMMAND
>    /dev/snd/controlC0:  karol      2618 F.... pulseaudio
>   CRDA: Error: [Errno 2] No such file or directory
>   Card0.Amixer.info:
>    Card hw:0 'Intel'/'HDA Intel at 0xe9660000 irq 22'
>      Mixer name : 'IDT 92HD81B1C5'
>      Components : 'HDA:111d76d5,1028040b,00100104'
>      Controls      : 26
>      Simple ctrls  : 16
>   Date: Fri Jul 16 13:36:04 2010
>   DistroRelease: Ubuntu 9.10
>   HibernationDevice: RESUME=UUID=cdf10c13-029f-401b-afed-f651ca0e2cbe
>   InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2)
>   MachineType: Dell Inc. Latitude E6510
>   NonfreeKernelModules: nvidia
>   Package: linux-image-2.6.31-22-generic-pae 2.6.31-22.60
>   PccardctlIdent:
>    Socket 0:
>      no product info available
>   PccardctlStatus:
>    Socket 0:
>      no card
>   ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-22-generic-pae
> root=UUID=2f511d08-c4e9-44e6-a1d2-5be6172b18c6 ro quiet splash
>   ProcEnviron:
>    PATH=(custom, user)
>    LANG=pl_PL.UTF-8
>    SHELL=/bin/bash
>   ProcVersionSignature: Ubuntu 2.6.31-22.60-generic-pae
>   RelatedPackageVersions:
>    linux-backports-modules-2.6.31-22-generic-pae 2.6.31-22.24
>    linux-firmware 1.26
>   SourcePackage: linux
>   Uname: Linux 2.6.31-22-generic-pae i686
>   dmi.bios.date: 05/28/2010
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A03
>   dmi.board.name: 0N5KHN
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA03:bd05/28/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn0N5KHN:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Latitude E6510
>   dmi.product.version: 0001
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/606238/+subscriptions
>