Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Jan 2001 17:04:46 -0500
From:      "Donald J . Maddox" <dmaddox@sc.rr.com>
To:        Bjarne Wichmann Petersen <mekanix@vip.cybercity.dk>
Cc:        dmaddox@sc.rr.com, FreeBSD-questions <freebsd-questions@FreeBSD.ORG>
Subject:   Re: Xfree 4.0.2 - mouse fixed... not really...
Message-ID:  <20010120170446.A998@cae88-102-101.sc.rr.com>
In-Reply-To: <200101202151.WAA84032@usr04.cybercity.dk>; from mekanix@vip.cybercity.dk on Sat, Jan 20, 2001 at 10:50:22PM %2B0100
References:  <200101201912.f0KJCtI24539@usr03.cybercity.dk> <200101201942.UAA71679@usr02.cybercity.dk> <20010120145322.A90461@cae88-102-101.sc.rr.com> <200101202013.f0KKDgu34319@usr03.cybercity.dk> <20010120152136.B349@cae88-102-101.sc.rr.com> <200101202026.VAA79619@usr02.cybercity.dk> <20010120153429.A402@cae88-102-101.sc.rr.com> <200101202057.VAA92424@usr01.cybercity.dk> <20010120160610.A390@cae88-102-101.sc.rr.com> <200101202151.WAA84032@usr04.cybercity.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
You're not quite getting it.  Moused translates mouse events from
whatever specific mouse device you use into MouseSystems protocol
and feeds it to /dev/sysmouse.

In other words, the driver you are using *is* /dev/psm0 and whatever
protocol is specific to your mouse.  There is a problem, however, in
that both X and moused want to handle mouse events, and only one
can be allowed to do so.

The solution is that moused handles *all* mouse events, and feeds
these events to /dev/sysmouse disguised as MouseSystems protocol.

This way, there is no conflict between the console mouse driver and
the X mouse driver.  See?

On Sat, Jan 20, 2001 at 10:50:22PM +0100, Bjarne Wichmann Petersen wrote:
> On Sat, 20 Jan 2001 16:06:10 -0500
> "Donald J . Maddox" <dmaddox@sc.rr.com> wrote:
> 
> > With the exception of the 'SysMouse' protocol stuff, I think the info
> > in the FAQ is still applicable w/4.0.2.  That is, all the stuff under
> > http://www.freebsd.org/FAQ/x.html#X-AND-WHEEL should still work with
> > no problems.
> 
> Now I've been reading up a bit about moused, sysmouse and all those FAQ etc.. "MouseSystems" seems to be the only protocol I can make to work, but it's not a clean way of doing it. "SysMouse" *is* as it's a "metadriver" idependant of what mouse/driver you use. Driver stuff is handled by moused.
> 
> MouseSystems also seems to be a driver for serial-mice and I'm using a PS/2-mouse *and* could kill off additional buttons (wheelmouse). My setup that worked for 4.0.1 *should* be correct, but doesn't work with 4.0.2. Why? 
> 
> I hardly use wheelmouse so using MouseSystems isn't really a big loss for me, *but* it annoys me terrible when something that should work doesn't! ;)
> 
> Bjarne
> --
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message


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




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