NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/biz/sco/general/4908

Internet Message Format | 1992-12-31 | 3.8 KB

Path: sparky!uunet!shady!kevin
From: [e-mail] (Kevin Smith)
Newsgroups: biz.sco.general
Subject: Re: Logitech C9 Serial Mouse at 9600 Baud
Keywords: logitech serial mouse
Message-ID: <[e-mail]>
Date: 31 Dec 92 19:52:40 GMT
References: <[e-mail]> <[e-mail]>
Organization: ShadeTree Software, Inc.
Lines: 65

In article <[e-mail]> [e-mail] (Michael B Garrett -- Chudys) writes:
>I would say to look in the mkdev mouse script, offhand. You should find the
>needed "stuff to change" in there. (I'm logged on now with a CP/M machine
>so I can't check it for you, but that's where I'd look first for clues).
>
>Query: Why in hell? What benefits are gained by running a serial mouse
>at 9600 baud? If it's on the typical COM1, and not on a co-processed
>multiport server, I'd expect it to have a detrimental effect systemwide.
>I could be wrong, but running a Telebit Worldblazer on COM2 at 9600+
>REALLY bogs my system down.....I dunno about a mouse, but I expect it
>would be much the same situation. Hard to say.
>
>'Shot

mkdev mouse allows you to pick one of the entries in
/usr/lib/event/devices and edits the /usr/lib/event/ttys file for the
tty associations.  It uses configure to add the driver to the kernel
(based on a fixed "mouse type" in the devices file)
(/etc/conf/cf.d/sevent) and manually creates the /etc/conf/node.d
files for idmkenv.

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.

A further note of justification (seems to be required).  I am running
a Pittsburgh Powercomputing X server on a #9Gxi-27 graphics adaptor
(1280x1024).  The PP X server gives me the option of using the SCO
event mechanism for mouse input or, given a supported serial mouse, it
will read the port directly.  In the latter case, with a logitech C9
mouse, it will program the port to 9600 baud.  This yields a
substantial improvement in mouse performance.  The mouse will move
smoothly around the screen instead of by leaps and bounds.  Using the
bus mouse through the event driver yields performance similar to the
direct connect 9600 baud serial mouse (i.e.  good).

I currently have two mice on my system.  A logitech bus mouse which I
use for SCO X windows and DOS/MERGE on my standard VGA screen and a
logitech serial mouse I use for the PP X windows.  This is because my
initial version of the PP X server supported only a directly
controlled serial mouse and did not support the SCO event stuff and
since it was reading the port directly it could not be shared with
anyone else on the system.  I now have two problems.  One, I have two
mice.  It's hard enough keeping one untangled from the phone cord and
other desk paraphanalia.  Second, I am out of slots on my motherboard
and would like to boot the bus mouse.  Otherwise I could toss the
serial mouse and stick with the bus mouse.

Since the mouse can operate at 9600 baud and the
/usr/lib/event/devices file seems to allow a way to configure it...
Can it be done? If so, how? What is the magic INIT string to put the
mouse in 9600 baud mode.  The doc that came with the mouse allows that
the mouse can be configured at 9600 baud but provides no actual info
on how to do it--They assume you are using their drivers and that you
will just pick 9600 from their configuration menu.

How about a free bus mouse to whoever has the answer :-)
--
        | Email - !shady!kevin uunet!shady!kevin [e-mail]
Kevin Smith | Voice - (+1) [phone]
        | Mail  - ShadeTree Software, Inc., 192 Capricorn Dr. #10,
        |         Somerville, NJ  08876, USA