On Tue, Apr 24, 2018 at 05:40:44PM +0300, IL Ka wrote:
> Hello Jason,
> Thank you.
>
> So, "wsmouse(4)"'s "/dev/wsmouse" multiplexer allows only exclusivie access
> now, right?
>
> Should not we also document it in wsmouse(4) like
> "/dev/wsmouse is multiplexer for all mice,
> and can only be acc
Hello Jason,
Thank you.
So, "wsmouse(4)"'s "/dev/wsmouse" multiplexer allows only exclusivie access
now, right?
Should not we also document it in wsmouse(4) like
"/dev/wsmouse is multiplexer for all mice,
and can only be accessed exclusively by eitherws(4)/synaptics(4) or
wsmoused(8)"
Ilya.
On Sun, Apr 22, 2018 at 05:45:26PM +0100, Jason McIntyre wrote:
> On Sun, Apr 22, 2018 at 01:27:40AM +0300, IL Ka wrote:
> > man wsmoused:
> > "wsmoused will happily coexist with the X Window System, provided that the
> > mouse device is supported by wsmouse(4). "
> >
> > I have wsmouse0 on pms0 (
On Sun, Apr 22, 2018 at 01:27:40AM +0300, IL Ka wrote:
> man wsmoused:
> "wsmoused will happily coexist with the X Window System, provided that the
> mouse device is supported by wsmouse(4). "
>
> I have wsmouse0 on pms0 (PS/2 controller emulation running on VirtualBox)
>
> When moused works on /
man wsmoused:
"wsmoused will happily coexist with the X Window System, provided that the
mouse device is supported by wsmouse(4). "
I have wsmouse0 on pms0 (PS/2 controller emulation running on VirtualBox)
When moused works on /dev/wsmouse, X reports
that device /dev/wsmouse is busy and mouse doe
