[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
The following reply was made to PR kern/47286; it has been noted by GNATS.
From: Iain Hibbert <plunky%ogmig.net@localhost>
Subject: Re: PR/47286
Date: Wed, 26 Dec 2012 18:13:47 +0000 (GMT)
Apologies for delay, but analysis of the PR is as follows
After some discussion with Martin which does not appear here, it appears
that the mouse was failing to authenticate with to the host. I suggested
disabling that (providing "-m none" to btdevctl), which revealed a problem
with the bthidev.c code, which did not handle the "none" linkmode
properly. This was fixed and the mouse does connect and the basic mouse
functions do work now
I was concerned that there could be different problem because
authentication failed, but it appears that Microsoft believe that this
is not required, and the Bluetooth HID specification does not mandate
that mice support it. Our btdevctl(8) program sets a linkmode of "auth"
for HID devices by default, and I added a comment to the manpage pointing
out that this may need to be modified manually. (will add something to the
I also increased the diagnostics in the bthidev(4) driver to print the
errno for failed connections, which would hopefully make it easier to
diagnose why a device was not connecting.
(will request this is pulled up to -6 and -5 branches)
Main Index |
Thread Index |