Re: kern/47286 (bluetooth mouse (MS Wedge Touch) not working)

[Iain Hibbert <plunky%rya-online.net@localhost>]

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

From: Iain Hibbert <plunky%rya-online.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: martin%NetBSD.org@localhost
Subject: Re: kern/47286 (bluetooth mouse (MS Wedge Touch) not working)
Date: Thu, 6 Dec 2012 11:38:18 +0000 (GMT)

 > bthidev0 at bthub0 remote-bdaddr 7c:1e:52:68:73:c1 link-mode auth
 > bthidev0: reportid 18 not configured
 > bthidev0: reportid 22 not configured
 > bthidev0: reportid 23 not configured
 > btms0 at bthidev0 reportid 26: 5 buttons, W and Z dirs.
 > wsmouse1 at btms0 mux 0
 > bthidev0: reportid 31 not configured
 > bthidev0: reportid 34 not configured
 > bthidev0: reportid 36 not configured
 > bthidev0: reportid 39 not configured
 >
 > Looks good so far, according to the guide it should now work.
 
 Yes, these non-configured reports are mostly Microsoft special features or
 inputs, and would likely need special handlers written
 
 #31 though is PAN (left/right scroll) which is handled by btms normally..
 I think this might be because the btms driver only attaches to
 Desktop/Mouse reports and this is showing up in a ConsumerControl/Mouse
 collection.
 
 however, even fudging the match routine will not help for this report ID
 as it would attach as a separate mouse and the driver doesn't allow for a
 mouse with no X and Y movements (it could be simple enough to fix that,
 the mouse driver is fairly minimal)
 
 ultimately, the HID framework needs a redesign I think, and the
 USB/Bluetooth drivers merging (since they are approximately the same) as
 currently the only way to get this kind of thing fully working is to
 provide a driver which attaches to the whole device, and duplicates the
 HID stuff (see btmagic(4))
 
 > But as soon as I move the mouse I get:
 >
 > bthidev0: disconnected
 > bthidev0: disconnected
 > ubt0: unknown handle 12! (losing track of 1 packet buffer)
 > bthidev0: disconnected
 > bthidev0: disconnected
 
 This one I'm not sure about but it should not happen.. the bthidev(4)
 driver is responsible for handling the connection, can you do that with
 sysutils/netbt-hcidump running (hcidump -w dump) and send me the dump
 file?
 
 iain