From owner-freebsd-hackers Fri Jun 19 04:24:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19691 for freebsd-hackers-outgoing; Fri, 19 Jun 1998 04:24:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19684; Fri, 19 Jun 1998 04:24:47 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id NAA00947; Fri, 19 Jun 1998 13:24:41 +0200 (CEST) (envelope-from sos) Message-Id: <199806191124.NAA00947@sos.freebsd.dk> Subject: Re: X-10 Mouse Remote patch In-Reply-To: <19980619070646.A10032@ct.picker.com> from Randall Hopper at "Jun 19, 98 07:06:46 am" To: rhh@ct.picker.com (Randall Hopper) Date: Fri, 19 Jun 1998 13:24:41 +0200 (CEST) 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 From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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