From owner-freebsd-mobile Fri Mar 10 16:14: 6 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 1C41837B9BF for ; Fri, 10 Mar 2000 16:14:02 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.3) id QAA45467; Fri, 10 Mar 2000 16:14:00 -0800 (PST) (envelope-from dhw) Date: Fri, 10 Mar 2000 16:14:00 -0800 (PST) From: David Wolfskill Message-Id: <200003110014.QAA45467@pau-amma.whistle.com> To: freebsd-mobile@freebsd.org Subject: Re: Touchpad (on NEC Versa 6030X), FreeBSD 4.0-RC (20000307), & XF86 3.3.6 In-Reply-To: <20000310011402.C4877@stat.Duke.EDU> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Date: Fri, 10 Mar 2000 01:14:02 -0500 >From: "Sean O'Connell" [I wrote about the hand-me-down NEC Versa 6030X & the behavior of the touchpad/mouse in FreeBSD 4.0-RC3 -- dhw] Sean suggested that I take a look at the flags for the psm0 device; in particular, the 0x0800 flag (PSM_CONFIG_FORCETAP). After playing around a little bit with both PSM_CONFIG_FORCETAP and PSM_FLAGS_FINGERDOWN (which I had -- erroneously, I now believe -- thought had something to do with a NEC Versa, based merely on noticing the name without examining the way it was used in more detail), I've managed to get a configuration that is almost making sense to me... at least, according to the "mouse" setup portion of XF86Setup. I'm running with a kernel that has PSM_FLAGS_FINGERDOWN (0x0001) on, but not PSM_CONFIG_FORCETAP (0x0800). I have moused running thus: moused -p /dev/psm0 -m 1=4 -m 2=1 with the intent that tapping the touchpad would be interpreted as button 1, the left-hand button would be treated as button 2, and the right-hand button would be treated as button 3. Further, XF86Setup believes that I'm using protocol "SysMouse" and device /dev/sysmouse with a "high" resolution; Emulate3Buttons is not selected. With this configuration, it seems that I can move the mouse around without changing the state of button 1; this is A Good Thing. :-) It seems to take a moderately forceful tap to do that, which is fine. (Perhaps "obviously intentional" would have been a better term than "forceful" -- it doesn't take all that much "force" per se; it does require doing something other than merely gliding the finger on the touchpad.) The problem, however, is that -- according to XF86Setup -- button 1 is normally depressed; tapping the touchpad releases it briefly. (That is, in XF86Setup's "mouse diagram", the left mouse button stays black unless I tap the touchpad, in whcih case it goes white... briefly.) This, of course, is a simple logic reversal of my understanding of the desired behavior. (The other buttons do seem to behave rationally.) So as soon as I have time, I plan to poke around in sys/isa/psm.c to see if I can either see something obviously silly in my configuration, or something I can do to hack the source to make it do something closer to useful for me. (I've tried setting Emulate3Buttons, and then there's no way to change the state of button 3, and the machine acts as if button 1 is continuously changing state. I found neither appealing.) (Yes, I've tried PSM_CONFIG_FORCETAP without PSM_FLAGS_FINGERDOWN, as well as neither flag defined and both flags defined. None of the combinations resulted in the behavior I think I want, as described above.) At least this should be hackable now.... :-} Thanks for your help so far, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message