From nobody Sun Aug 15 17:51:58 2021 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 44014176B35B for ; Sun, 15 Aug 2021 17:51:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GnlH21NKRz3qCw for ; Sun, 15 Aug 2021 17:51:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 17D631A66D for ; Sun, 15 Aug 2021 17:51:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 17FHpwEU014613 for ; Sun, 15 Aug 2021 17:51:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 17FHpwNp014612 for bugs@FreeBSD.org; Sun, 15 Aug 2021 17:51:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 257867] Mouse 4D+ erratic move (psm.c and moused.c) Date: Sun, 15 Aug 2021 17:51:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: Unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: franz.arnold@live.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257867 Bug ID: 257867 Summary: Mouse 4D+ erratic move (psm.c and moused.c) Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: franz.arnold@live.com Mouse 4D+ is erratic when moving backward (negative X or negative Y). Cursor jumps instantly to position (0,0) under a GUI (Graphic User Interface). Mouse move could go even crazier when it is enabled for terminal text, selecting and doing things under no clearly understandable reason. This seems to be affecting both Free BSD and DragonFly BSD I've tested so f= ar (the late two main releases of both OS). In both case, after forcing the boot probe to ignore actual mouse or forcing mouse protocol to be a regular PS/2 mouse, it seemed to work (move cursor) = as expected. I've researched several Discussion Groups and Forums for months without fin= ding useful solution. Also have researched both OS Source Code and found somethi= ng interesting that might be related to that strange behavior. First issue: In the psm.c, searching for the keyword MOUSE_MODEL_4DPLUS, on line 5103, we can find "if ((x < 16 - 256) && (y < 16 - 256))". But in moused.c, searching for the same MOUSE_MODEL_4DPLUS, on line 2289, we can find "if ((act->dx < 16 - 256) && (act->dy > 256 - 16))". Why would there be a different calculation for testing and decision regardi= ng mouse move? Second issue: In both source codes (psm.c line 5103; moused.c line 2290) we can find "x = =3D y =3D 0" and "act->dx =3D act->dy =3D 0" respectively. What is happening actually? What is being interpreted as backward mouse mov= e? Is it correct for the 4D+ Mouse protocol? I am not experienced in hardware communication protocol, which applies PS/2 mouse protocol. Hope this finding could useful, specially other users trying BSD with old hardware like myself (which is not a bad idea). Please, could someone more knowledgeable about PS/2 mouse and binary protoc= ol check this? Many thanks in advance. --=20 You are receiving this mail because: You are the assignee for the bug.=