Actully lawson your origninal suggestion was wrong.
I checked my source and what I had coded was
correct.
I rebooted my box with box devices (serial & ps2)
in place and linux detected the new hw. It asked
if i wanted it configured and I clicked on ok. Before
the boot i also went into the bios and forced the
com ports to be enabled. The code worked first time
after that. The upshot is that it was configuration
problem more than a coding problem.
Thanks again and sorry to bug you guys,
-mya
[EMAIL PROTECTED] wrote:
>
> On Sat, 1 Apr 2000, Marwan Ansari wrote:
>
> > Nuts, stupid mastake I know, I should have
> > read the example more, but it was getting late, honest!
> >
> > I did try an example of non-canocal communications with
> > and it got the same results as I got here. Maybe I need
> > a better question. Ok, so as you know the ps/2 is plugged
> > in at boot time. That is the mouse used by the window system.
> > When I plug the mouse (or any device really) into the serial
> > port do I have to "wake it up" ? I know if i query the mouse
> > by toggling the DTR the mouse will send back an 'M' . Thats
> > all fine and good but do I need to toggle the DTR before I can
> > accept input from the mouse on the serial port?
> >
> > Thanks again for you help,
> > -mya
> >
> Mice are a lot like virii. They are pretty simple, but there are a
> _lot_ of different kinds. From man gpm:
>
> -o lines
> Toggle modem lines. The lines argument
> can be
> ``dtr'', ``rts'' or ``both''. This is
> needed for
> some strange serial mice.
>
> Perhaps a PS/2 mouse connected to a serial line has to behave
> differently than it would connected to a PS/2 port, and needs to see a
> toggle on dtr to know it is connected to a serial port? But mice don't
> _have_ to have a reason for what they do.
>
> Lawson
>
> >> Build a better mousetrap, and the world will build a better mouse.>>
> - Proverbs of Hell Revisited
-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to [EMAIL PROTECTED]
