Date: Mon, 14 Sep 2015 18:09:23 +0100 (BST) From: Iain Hibbert <plunky@ogmig.net> To: Dirk Engling <erdgeist@erdgeist.org> Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org> Subject: Re: Apple Magic Mouse Message-ID: <alpine.NEB.2.11.1509141802300.690@galant.ogmig.net> In-Reply-To: <55F60ED8.8080203@erdgeist.org> References: <1437909200.57929.3.camel@yandex.com> <alpine.NEB.2.11.1508092034290.5638@galant.ogmig.net> <55F4362A.4050203@erdgeist.org> <CAFPOs6p%2BEZDctPodY6DBbnhfZQFz%2Bo0uKSRvvqQBcM1QL3ACXw@mail.gmail.com> <55F60ED8.8080203@erdgeist.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 14 Sep 2015, Dirk Engling wrote: > On 12.09.15 19:53, Maksim Yevmenkin wrote: > > > i think it should be possible to teach bthidd to make another sdp > > request to pull device id sdp record (if available). if apple mouse > > answers it then it should very easy to identify it and enable all the > > features. > > Apples magic mouse indeed answers the SDP request for its Device ID > Service Record. > > Find attached a first patch that adds a vendor, product and version > member in the bthid_session object that is filled after both connections > for the session were attached. > > This is done in a new function session_get_devid that issues and handles > the SDP requests. > > There's also a new hid_initialise function, that gets a chance to take a > look at those new members and initialise devices based on those information. My advice is, to put that code in bthidcontrol, which already queries the device, and add product-id and vendor-id fields to the bthidd.conf file. that then solves your issue about the libsdp blocking read/write calls, since it knows the information before it starts. iain
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.NEB.2.11.1509141802300.690>