Re: bin/53049: wsmoused not working: ioctl(WSDISPLAYIO_PUTWSCHAR) fail

[Michael van Elst <mlelstv%serpens.de@localhost>]

The following reply was made to PR bin/53049; it has been noted by GNATS.

From: Michael van Elst <mlelstv%serpens.de@localhost>
To: bernward.pub%arcor.de@localhost
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: bin/53049: wsmoused not working: ioctl(WSDISPLAYIO_PUTWSCHAR)
 fail
Date: Sun, 25 Feb 2018 15:45:21 +0100

 On Sun, Feb 25, 2018 at 12:49:40PM +0000, bernward.pub%arcor.de@localhost wrote:
 > Hello Michael,
 > 
 > I tested this and can confirm that setting the right X console in
 > /etc/wsmoused.conf makes wsmoused quiet, when I switch to X.
 > So, with the right set configuration file /etc/wsmoused.conf,
 > there are no more disturbances to the use of X.
 > 
 > Again, the classification of this PR should be unchanged, because
 > the intended function of wsmoused is still not given at all,
 > while it disturbs the text console by unnecessarily using cpu time.
 > 
 > A possibly interesting observation aubout the used cpu time of wsmoused
 > and syslogd via top, now with the right setting only on text console:
 > Heavy mouse movements for about 5 seconds let both values go up over 40% cpu usage.
 
 Sure, the mouse sends movement events at 100-400 Hz. Each movement
 triggers wsmoused which logs an error to syslog. That's a huge overhead.
 
 As I said, wsmoused does not work on framebuffer consoles. It works on
 the assumption that the console has a transparent character / attribute
 memory which isn't necessarily true for graphical consoles.
 
 
 
 Greetings,
 -- 
                                 Michael van Elst
 Internet: mlelstv%serpens.de@localhost
                                 "A potential Snark may lurk in every tree."