From owner-freebsd-current Wed Jun 26 00:00:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA13144 for current-outgoing; Wed, 26 Jun 1996 00:00:01 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA13098 for ; Tue, 25 Jun 1996 23:59:54 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id IAA26099; Wed, 26 Jun 1996 08:59:12 +0200 Message-Id: <199606260659.IAA26099@ra.dkuug.dk> Subject: Re: moused conflicts with X11 To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 26 Jun 1996 08:59:12 +0200 (MET DST) Cc: freebsd-current@FreeBSD.ORG, dawes@rf900.physics.usyd.edu.au In-Reply-To: <199606252014.WAA19927@uriah.heep.sax.de> from "J Wunsch" at Jun 25, 96 10:14:50 pm From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to J Wunsch who wrote: > > As sos@FreeBSD.org wrote: > > > Hmm, that could easily be arranged, I could easy make a minor# on > > syscons send out mouse events, no problem in that end... > > Do we want that ?? > > Not _that_, but this. :-) > > Don't make it dependant on syscons. It's some sort of a super-driver > layered on top of either sio or mse or psm, but only losely related to > the console driver itself. You could actually even have a mouse but > don't have a keyboard or graphics card, even though it would hardly > make sense. You have a point there, except I dont like the "superdriver" idea.. A generice mousedevice that does what syscons does now would be just fine. The only problem I have with that is that the interface between that driver and the console driver would be an ugly SOAB... But if that's what it takes I'll rip out that part of syscons and make it a pseudo driver instead. > Anyway, i'm (naturally :) more concerned about pcvt > users. We should avoid things that would require more console-driver > dependant hacks in the Xserver. (The Xserver would need hacks for > both mouse scenarios anyway, for a reasonable transition time.) I (naturally:)) dont care about pcvt problems with this, that particular set of problems would never arise if we had _one_ consoledriver, but thats history. There is no easy solution to that I guess. However I dont see that the Xserver should be changed, as they will see /dev/mouse as a say mousesystems mouse, no matter what mouse actually is on the system. That would also ease the X installation for J. Randomuser. And besides I dont see the need for Yet Another Mouse Interface (YAMI), when we can just use one of the de facto standards. We also would have a BIG problem with commercial progs that way, so lets not get that insane... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time.