Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 23 Sep 2018 13:56:16 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 231058] no support for active PS/2 multiplexing results in erratic behaviour of Synaptics touchpad on HP 8560w
Message-ID:  <bug-231058-227-medd8brXmf@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-231058-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-231058-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231058

Vladimir Kondratyev <wulf@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wulf@freebsd.org

--- Comment #1 from Vladimir Kondratyev <wulf@freebsd.org> ---
(In reply to Michael Figiel from comment #0)
> I think the root cause of the 0x46 id is that FreeBSD doesn't
> support active PS/2 multiplexing.
Wow! I was not aware of 'active PS/2 multiplexing' when committed 0x46 hack.
Unfortunately, now I do not have access to such a hardware to reimplement i=
t in
a right way.

> multiplexing controller operated in legacy (non-multiplexing)
> mode with more than one aux device might garble some of the
> data passed to the host.
I don`t think so. Trackpoint support code in synaptics driver expects
trackpoint to be attached via special passthrough interface which does
Generic->Synaptics protocol conversion. It (driver) it its current state ju=
st
can not decode generic mouse protocol.

> I'm not sure if it is really worth the effort to implement the multiplexi=
ng
Proper multiplexing implementation requires a lot of changes in both atkbd =
and
psm drivers. I think it is overkill. The simpler way is to enable multiplex=
ing
only for synaptics devices and just only for configuring/querying stage and
return to legacy mode after. trackpad/trackpoint packet separation problem
should be solved in that case.

> that the few machines which use it will die of old age pretty soon
0x46 hack was made for 2013 year model. It is not so old to die quickly.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231058-227-medd8brXmf>