Re: synaptics touchpad + mouse taps = trouble

On Thu, Oct 1, 2009 at 12:07 PM, David Horn <dhorn2000_at_gmail.com> wrote:
> On Thu, Oct 1, 2009 at 8:36 AM, Stephen Montgomery-Smith
> <stephen_at_missouri.edu> wrote:
>> David Horn wrote:
>>>
>>> I currently have a laptop running FreeBSD 8/Stable RC1 r197621 (amd64)
>>> that happens to have a synaptics touchpad.  On this particular
>>> laptop(Inspiron 1520), the placement of the touchpad means that I will
>>> inevitably accidentally hit it while typing, and I have found that I
>>> always need to disable the "mouse taps" in order to have the touchpad
>>> usable for me.
>>
>> I have an Inspiron 1525.  After struggling with this for a long time, I
>> found that the following entry in /etc/rc.conf did the trick
>>
>> moused_flags="-3 -m 11=4 -A 2"
>
> Interesting.  This maps physical button #4 to buttton  #11.  I will
> take a look again, but in my psm device, I never saw button 4 events,
> just button #1 and button #3 under generic psm mode. Mouse taps always
> showed up as button #1 so it was impossible to differentiate between
> tap #1 and real #1. (unless something like moused was mapping #4 to
> #1, hmm something to investigate)
>
> Were you running psm/generic or psm/Extended Synaptics or using ums0 ?
> Does your ums0 mouse show up as Broadcom 4503 ?
>
>>
>> It is the "-m 11=4" that did it.  On my computer, it isn't really a
>> "synaptics" touchpad, but some other brand.
>>
>> Hopefully it will work for you.
>>
>> Stephen
>>
>
> Here is the hw.usb.ums.debug=99 data after a usbconfig -u 0 -a 5 reset
>
> Oct  1 11:33:43 dhorn-1520 kernel: ums0: <Broadcom Corp product
> 0x4503, class 0/0, rev 2.00/1.00, addr 5> on usbus0
> Oct  1 11:33:43 dhorn-1520 kernel: ums0: 3 buttons and [XY] coordinates ID=2
> Oct  1 11:44:56 dhorn-1520 kernel: ums0: at uhub7, port 3, addr 5 (disconnected)
> Oct  1 11:44:56 dhorn-1520 kernel: ums_detach:661: sc=0xffffff0001feb000
> Oct  1 11:44:57 dhorn-1520 kernel: ums_probe:365:
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:503: sc=0xffffff00041d1000
> Oct  1 11:44:57 dhorn-1520 kernel: ums0: <Broadcom Corp product
> 0x4503, class 0/0, rev 2.00/1.00, addr 5> on usbus0
> Oct  1 11:44:57 dhorn-1520 kernel: ums0: 3 buttons and [XY] coordinates ID=2
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:599:
> sc=0xffffff00041d1000, index=0
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:601: X    8/8 id=2
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:603: Y    16/8 id=2
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:605: Z    0/0 id=0
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:607: T    0/0 id=0
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:609: W    0/0 id=0
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:614: B1   0/1 id=2
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:614: B2   1/1 id=2
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:614: B3   2/1 id=2
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:599:
> sc=0xffffff00041d1000, index=1
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:601: X    0/0 id=0
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:603: Y    0/0 id=0
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:605: Z    0/0 id=0
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:607: T    0/0 id=0
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:609: W    0/0 id=0
> Oct  1 11:44:57 dhorn-1520 kernel: ums_attach:617: size=4, id=2
> Oct  1 11:44:57 dhorn-1520 kernel: ums_open:771:
> Oct  1 11:44:57 dhorn-1520 kernel: ums_open:771:
> Oct  1 11:44:57 dhorn-1520 kernel: ums_ioctl:808:
>
> No additional events on mouse movement/buttons, but on moused startup I get
>
> Oct  1 12:01:23 dhorn-1520 kernel: ums_open:771:
> Oct  1 12:01:23 dhorn-1520 kernel: ums_open:771:
> Oct  1 12:01:23 dhorn-1520 kernel: ums_ioctl:808:
>
>
> running moused -df -p /dev/ums0 -t auto gives no mouse events to
> movement/buttons at all.
>
> --Dave H
>
OK, I figured out the ums0 problem.   <sigh>

It seems that Broadcomm 450x is a virtualized HID interface from the
BCM 2045B2 Blueooth Chip to provide HID functions (4502 = ukbd,
4503=ums)

This is *supposed* to be a method to present simplified interfaces for
Bluetooth mouse/kbd via USB rather than the OS having to initialize a
bluetooth stack and device.   Long story short is that ums0 is not the
device I thought it was, and the synaptics touchpad is only exposed
via psm device.

Still investigating to see if there is a better way to improve the
default case of synaptics with hal and xf86-driver-synaptics,

Sorry for the noise.

---Dave H