home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!xenitec!news
- From: belal@sco.COM (Bela Lubkin)
- Newsgroups: biz.sco.general
- Subject: Re: Logitech C9 Serial Mouse at 9600 Baud
- Message-ID: <9212311731.aa13710@scoke.sco.COM>
- Date: 1 Jan 93 01:31:17 GMT
- Sender: news@xenitec.on.ca (xenitec.on.ca News Administrator)
- Organization: [resent by] The SCOGEN gateway and Propagation Society
- Lines: 41
- Resent-From: mmdf@xenitec.on.ca
- Submit-To: scogen@xenitec.on.ca
- Precedence: bulk
-
- Kevin Smith wrote:
-
- > It doesn't appear that the STTY and INIT strings are in any way
- > configured into the kernel. For a serial mouse, then, this must be
- > handled by the event library calls (By the way, I seem to be missing
- > my ev_open() man pages). The sequence would be, I believe, to apply
- > the STTY to the port then send the INIT string, after which,
- > everything should be ready to go.
-
- I've included ev_open(S) below (compressed, uuencoded -- it has
- formatting which will not necessarily transport correctly over the
- Internet).
-
- It is ev_open() which sends the INIT string to the mouse port. The
- string itself is meaningful to the mouse, not the kernel. The serial
- mouse init strings in /usr/lib/event/devices all have the form "*nNx",
- where "x" varies depending on the mouse mode to be used. So presumably
- either "n" or "N" is the baud rate specifier. I'd say, experiment with
- it. With nothing using the serial mouse, do this:
-
- on multiscreen 1: sleep 10000 < /dev/tty1a # keep the port open
- on multiscreen 2: hd /dev/tty1a # log mouse output
- on multiscreen 3: stty 1200 < /dev/tty1a
- on multiscreen 3: echo "*nNU\c" > /dev/tty1a # init to default mode
- <move mouse around, look at the hex output on screen 2, get an idea of
- what it's supposed to look like when it's working correctly>
- on multiscreen 3: stty 2400 < /dev/tty1a
- on multiscreen 3: echo "*nOU\c" > /dev/tty1a # init 2400??
- <move mouse around: is it making sense on screen 2?>
-
- I learned from the ev_open() source that the baud rate is set before the
- init string is sent. So I'm guessing that the mouse automatically
- handles varying baud rates for the init string, which probably means the
- first two characters are just to get it in sync. So the third is
- probably the baud rate, thus the guess of "*nOU" to initialize the same
- mouse mode at 2400bps.
-
- Anyone with tech docs for a Logitech serial mouse should be able to
- answer this instantly...
-
- >Bela<
-