Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Jun 1998 13:24:41 +0200 (CEST)
From:      Søren Schmidt <sos@FreeBSD.ORG>
To:        rhh@ct.picker.com (Randall Hopper)
Cc:        sos@FreeBSD.ORG, nirva@ishiboo.com, hasty@netcom.com, yokota@zodiac.mech.utsunomiya-u.ac.jp, multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG, hasty@rah.star-gate.com
Subject:   Re: X-10 Mouse Remote patch
Message-ID:  <199806191124.NAA00947@sos.freebsd.dk>
In-Reply-To: <19980619070646.A10032@ct.picker.com> from Randall Hopper at "Jun 19, 98 07:06:46 am"

next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Randall Hopper who wrote:
> Sren Schmidt:
>  |Yep it will endeed, this is the way to do it guys, the current hacks
>  |to moused are, well, nicely put, GROSS!!
> ...
>  |Guys you need to do a little design now and then, not all these 
>  |quick hacks, if not FreeBSD will end up being like the L word :)
> 
> On the subject of hacks and design, when I found out this is how
> /dev/sysmouse works a few weeks ago, I was somewhat disappointed:
> 
> 
>                        /----> syscons-specific ---->
>                       /           back door          \
>  serial port -> moused                                ---> /dev/sysmouse -> X11
> 
> 
> This having-to-change-the-console-driver to extend the sysmouse protocol
> crossed several cleaner design options off my list at the start.  
> 
> Why should the console driver have any special status?  Just another mouse
> client, right?

Nope.

Moused is ONLY a frontend in the mouse system as such. Moused is a deamon
that nows about different mouse protocols, and not much else. This is
because we dont want mouse specific code in the kernel.
Moused delivers the mouse events to syscons, the console driver, which
then in turn multiplexes the mouseevents between the active virtual
screens, provides support for sending a signal to a process when the
mouse moves or a button is pressed. I also provides a generalize 
mouse on /dev/sysmouse that oldstyle apps like X can use, otherwise
you can only have ONE apps using the mouse, now it can be shared between
the virtual consoles.
So, there is good technical resons why the moused/syscons system is
designed the way it is.
All I ask for is that you do the same thing for things you put into
the system, if the design/functionality isn't easy to understand, 
then ask the author/maintainer and I'm sure you will get an explantion
on how things are supposed to work.

I repeat again, putting X10 specific stuff into moused is wrong.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
                Even more code to hack -- will it ever end?
..

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



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