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 /dev/wsmouse, X reports > that device /dev/wsmouse is busy and mouse does not work. > > To investigate it, I tried to open(2) it and perror(3) said "Device busy": > I then stopped wsmoused, and open(2) worked. > So, X is right: it can't share /dev/wsmouse with wsmoused. > > I then created custom ServerLayout for X > with InputDevice backed by "ws" driver pointing to "/dev/wsmouse0" > > and it worked. > > So, X can access my mouse directly (via /dev/wsmouse0) but not > via multiplex (/dev/wsmouse) > > I have 2 approaches to fix it: > 1) Update wsmoused(8) man page and write that user must stop it before X > 2) Patch "ws" to probe first N mice: it will start X with mouse even if > wsmoused runs > > Which one should I take? > > I also suggest to move following phrase from wsmoused(8) to wsmouse(4) man: > "/dev/wsmouse (the multiplexer device that receives all mouse events from > all wsmouse compatible mice on the system)" > > This information is vital to understand how wsmouse works, and it is not > easy to find now. > Should I do that? > > > Ilya.
at some point, behaviour changed so that you could have one, but not both. that was deliberate. i think we should probably just alter the text that says you can have both. devs? jmc
