From owner-freebsd-hackers Thu Jun 18 10:07:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08413 for freebsd-hackers-outgoing; Thu, 18 Jun 1998 10:07:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA08395; Thu, 18 Jun 1998 10:07:13 -0700 (PDT) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Thu, 18 Jun 1998 13:05:34 -0400 (EDT) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA22898; Thu, 18 Jun 98 13:05:33 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id NAA07558; Thu, 18 Jun 1998 13:05:10 -0400 Message-Id: <19980618130510.A7551@ct.picker.com> Date: Thu, 18 Jun 1998 13:05:10 -0400 From: Randall Hopper To: Danny Dulai Cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG, Kazutaka YOKOTA , Amancio Hasty Subject: Re: X-10 Mouse Remote patch Mail-Followup-To: Danny Dulai , multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG, Kazutaka YOKOTA , Amancio Hasty 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980618124731.02987@bleep.ishiboo.com>; from Danny Dulai on Thu, Jun 18, 1998 at 12:47:31PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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-hackers" in the body of the message