Date: Fri, 2 Oct 2009 13:43:33 -0400 From: David Horn <dhorn2000@gmail.com> To: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: synaptics touchpad + mouse taps = trouble Message-ID: <25ff90d60910021043k359c5af8r53f73d4aa210c49@mail.gmail.com> In-Reply-To: <25ff90d60910010907la9f8227oecee2aec0b492572@mail.gmail.com> References: <25ff90d60910010138l24e83470v390e8c0271f332f7@mail.gmail.com> <4AC4A26A.6040101@missouri.edu> <25ff90d60910010907la9f8227oecee2aec0b492572@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 1, 2009 at 12:07 PM, David Horn <dhorn2000@gmail.com> wrote: > On Thu, Oct 1, 2009 at 8:36 AM, Stephen Montgomery-Smith > <stephen@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. =A0On 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. =A0After struggling with this for a long time, = I >> found that the following entry in /etc/rc.conf did the trick >> >> moused_flags=3D"-3 -m 11=3D4 -A 2" > > Interesting. =A0This maps physical button #4 to buttton =A0#11. =A0I 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=3D4" that did it. =A0On 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=3D99 data after a usbconfig -u 0 -a 5 reset > > Oct =A01 11:33:43 dhorn-1520 kernel: ums0: <Broadcom Corp product > 0x4503, class 0/0, rev 2.00/1.00, addr 5> on usbus0 > Oct =A01 11:33:43 dhorn-1520 kernel: ums0: 3 buttons and [XY] coordinates= ID=3D2 > Oct =A01 11:44:56 dhorn-1520 kernel: ums0: at uhub7, port 3, addr 5 (disc= onnected) > Oct =A01 11:44:56 dhorn-1520 kernel: ums_detach:661: sc=3D0xffffff0001feb= 000 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_probe:365: > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:503: sc=3D0xffffff00041d1= 000 > Oct =A01 11:44:57 dhorn-1520 kernel: ums0: <Broadcom Corp product > 0x4503, class 0/0, rev 2.00/1.00, addr 5> on usbus0 > Oct =A01 11:44:57 dhorn-1520 kernel: ums0: 3 buttons and [XY] coordinates= ID=3D2 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:599: > sc=3D0xffffff00041d1000, index=3D0 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:601: X =A0 =A08/8 id=3D2 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:603: Y =A0 =A016/8 id=3D2 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:605: Z =A0 =A00/0 id=3D0 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:607: T =A0 =A00/0 id=3D0 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:609: W =A0 =A00/0 id=3D0 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:614: B1 =A0 0/1 id=3D2 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:614: B2 =A0 1/1 id=3D2 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:614: B3 =A0 2/1 id=3D2 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:599: > sc=3D0xffffff00041d1000, index=3D1 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:601: X =A0 =A00/0 id=3D0 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:603: Y =A0 =A00/0 id=3D0 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:605: Z =A0 =A00/0 id=3D0 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:607: T =A0 =A00/0 id=3D0 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:609: W =A0 =A00/0 id=3D0 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_attach:617: size=3D4, id=3D2 > Oct =A01 11:44:57 dhorn-1520 kernel: ums_open:771: > Oct =A01 11:44:57 dhorn-1520 kernel: ums_open:771: > Oct =A01 11:44:57 dhorn-1520 kernel: ums_ioctl:808: > > No additional events on mouse movement/buttons, but on moused startup I g= et > > Oct =A01 12:01:23 dhorn-1520 kernel: ums_open:771: > Oct =A01 12:01:23 dhorn-1520 kernel: ums_open:771: > Oct =A01 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 =3D ukbd, 4503=3Dums) 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25ff90d60910021043k359c5af8r53f73d4aa210c49>