From owner-freebsd-questions Sun Sep 3 11:31:23 2000 Delivered-To: freebsd-questions@freebsd.org Received: from inconnu.isu.edu (inconnu.isu.edu [134.50.8.55]) by hub.freebsd.org (Postfix) with ESMTP id B434C37B43F for ; Sun, 3 Sep 2000 11:31:16 -0700 (PDT) Received: from localhost (galt@localhost) by inconnu.isu.edu (8.9.3/8.9.3) with ESMTP id MAA10389; Sun, 3 Sep 2000 12:30:14 -0600 Date: Sun, 3 Sep 2000 12:30:14 -0600 (MDT) From: John Galt To: rob Cc: "questions@FreeBSD.ORG" Subject: Re: Synaptics touchpad config program\ Python hacking In-Reply-To: <39B229C7.9AA0DA37@home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There were PS/2 versions of the synaptics, as well as 9-pin serial. Micro Innovations put out a keyboard/touchpad that uses the serial version (in fact the reason I know is I looked at my own MI keyboard...:), however I'm thinking that most notebooks quite logically used the ps/2 protocol (I don't think that anyone would've used the term "logically" WRT PS/2 when the IBM PS/2 came out :). I'm not a python programmer myself, but I'm thinking that the method used in communicating with the PS/2 port are almost exactly the same as the cuaaX ports, so I doubt that this has much bearing on the final result other than a "heads up" that there is more than one flavor (as is the case with almost all mice any more). On Sun, 3 Sep 2000, rob wrote: > I get confused with Linux. On this machine it is /dev/psm0. I have to > kill moused to be able to access it. Rob. > > John Galt wrote: > > > > FYI, some synaptics devices (like mine) are on cuaaX (serial)... > > > > On Sat, 2 Sep 2000, rob wrote: > > > > > First I need to see if I can communicate with /dev/psaux via the Python > > > console. I need to start brewing some coffee to build up the > > > initiative. So once I start hacking on this, I assume I'm in the > > > jurisdiction of some other mailing list. What would be appropriate? > > > Rob. > > > > > > > > > > > > > > > John Galt wrote: > > > > > > > > THANKYOUTHANKYOUTHANKYOU!!!!!! Can I assist in the test? > > > > > > > > On Sat, 2 Sep 2000, rob wrote: > > > > > > > > > Someone asked a week or so ago about the Synaptics touch pad 'driver'. > > > > > I have the Linux source here. It is not really a driver, but a config > > > > > utility which sets up the pad so that the extra functions work. So it > > > > > looks pretty simple so I've decided I will try to port it. > > > > > Unfortunately it uses the deprecated 'ftime' function, and also > > > > > 'getopt_long' which doesn't seem to work even though getopt.h on my > > > > > system seems to include this. > > > > > > > > > > I'm more of a Python programmer. Maybe I can write Python config > > > > > program. Rob. > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > -- > > > > When you are having a bad day, and it seems like everybody is trying to > > > > tick you off, remember that it takes 42 muscles to produce a frown, but > > > > only 4 muscles to work the trigger of a good sniper rifle. > > > > > > > > Who is John galt? Galt@inconnu.isu.edu, that's who! > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > -- > > When you are having a bad day, and it seems like everybody is trying to > > tick you off, remember that it takes 42 muscles to produce a frown, but > > only 4 muscles to work the trigger of a good sniper rifle. > > > > Who is John galt? Galt@inconnu.isu.edu, that's who! > -- There is an old saying that if a million monkeys typed on a million keyboards for a million years, eventually all the works of Shakespeare would be produced. Now, thanks to Usenet, we know this is not true. Who is John Galt? galt@inconnu.isu.edu, that's who! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message