Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Jun 1998 13:05:10 -0400
From:      Randall Hopper <rhh@ct.picker.com>
To:        Danny Dulai <nirva@ishiboo.com>
Cc:        multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG, Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>, Amancio Hasty <hasty@rah.star-gate.com>
Subject:   Re: X-10 Mouse Remote patch
Message-ID:  <19980618130510.A7551@ct.picker.com>
In-Reply-To: <19980618124731.02987@bleep.ishiboo.com>; from Danny Dulai on Thu, Jun 18, 1998 at 12:47:31PM -0400
References:  <19980601194116.A25497@ct.picker.com> <199806180122.KAA04952@zodiac.mech.utsunomiya-u.ac.jp> <19980618015038.40458@bleep.ishiboo.com> <19980618062844.E3160@ct.picker.com> <19980618124731.02987@bleep.ishiboo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Danny Dulai:
 |> I have noticed that the spurious events seem to only be mouse button or
 |> motion events.  So I plan to look for a cheap serial port ISA board to plug
 |> in and just give MouseRemote its own serial port.  I know that works fine
 |> as I ran that way originally.  Then I won't care about the mouse event
 |> noise.
 |
 |Hrm, I'm using my second com port for just the x10 remote. Are you
 |suggesting to just use the /dev/cuaa1 instead of socket that moused
 |creates?

No, nothing of the kind.  Still fire up a moused on the com port that the
MouseRemote is attached to.  That way the interface to the MouseRemote is
uniform, regardless of how it's plugged up (i.e. the /var/run/MouseRemote
UNIX domain socket moused manages.

Randall

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-multimedia" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980618130510.A7551>