Date: Mon, 23 Mar 2015 00:25:48 -0700 From: Waitman Gobble <gobble.wa@gmail.com> To: Iain Hibbert <plunky@ogmig.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: register HID with SDP error Message-ID: <CAFuo_fyL-ZS6rBUR1bnLJ2m6ZoLoO=yq7JcY=AvhshNm=9uMqw@mail.gmail.com> In-Reply-To: <alpine.NEB.2.11.1503230646520.15407@galant.ogmig.net> References: <CAFuo_fy9xRU2T3GUPY8116yZCUd8sL9pBQ9ixXnMwO56niJFog@mail.gmail.com> <CAFuo_fzB3A5L3vivH7Z80OEoBtVEHftEYE4LUkhnrkguzL5GDA@mail.gmail.com> <CAFuo_fzrk%2BWLXivZrnTsGQD%2BS7mq%2BUSXB7Mn6%2BJT=y64JakGSw@mail.gmail.com> <CAFPOs6q3iVcNthF=S--UgTm=5wA0HM6coqB7AcmCKb=55OWdTQ@mail.gmail.com> <CAFuo_fxgBVKxmzbJs%2B-XDz%2Bu4tb2_i3eYXSa-oiOoU%2BQD6ApwQ@mail.gmail.com> <CAFPOs6r_D7bcGCMP_bP%2BQtZgKt7Oj5jRJ2v872RODekn%2B6xv1Q@mail.gmail.com> <CAFuo_fwPuaD4bYwfZou0RBswZsTmdtVZA1B2GqUdo3ZJJiWRQg@mail.gmail.com> <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com> <CAFuo_fye5RWNtjsutHa%2BbXL0AYHYRpJxW-b=48o0iMwX227wdA@mail.gmail.com> <alpine.NEB.2.11.1503170658130.4414@galant.ogmig.net> <CAFuo_fx47uRC-eKD_KtsSsrMCQZauyHyCOgRxGbtp_WEZ49o_Q@mail.gmail.com> <alpine.NEB.2.11.1503171759510.4792@galant.ogmig.net> <CAFPOs6omaOOOumNk2Zg=YBgK9cy7JumOZ6k-89oTbVw-3PgAvg@mail.gmail.com> <CAFuo_fy%2BdmpcswwLMV3LaGGkN6VyQ%2B=ieEzYUT=omSLkhS8=EA@mail.gmail.com> <alpine.NEB.2.11.1503230646520.15407@galant.ogmig.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 23, 2015 12:06 AM, "Iain Hibbert" <plunky@ogmig.net> wrote: > > On Sun, 22 Mar 2015, Waitman Gobble wrote: > > > >> btw .. if you use sdpcontrol(1) to query the local SDP server (see -l) > > >> then hcidump will not see anything of the interchange, since it does not > > >> go through the Bluetooth stack. > > > > > > absolutely correct > > > > I'm tracking down a client connection problem, maybe this is causing > > the issue... > > I doubt that is causing anything, exactly > > > checking it out. > > > > https://gist.github.com/waitman/c51ea08ebb6a2898f33f > > > > client gives up and never opens PSM channel 17 or 19 > > you didn't say what client it is, and why it should try to connect to HID? > Not all will, of course.. It may be more pertinient that when it searches > for L2CAP, it did not discover any services? Searching for L2CAP is a lazy > way to enumerate services, as many devices failed to provide a proper > browse group, but if a device is looking for HID then I would expect it to > search for HID? Yes, it may be lazy perhaps. However, I have noticed that when the l2cap query results are returned (see my note about commenting out a line if code to get a response sent back).. then it starts working as HID keyboard on android phone, Windows installs a device driver and registers as keyboard, and mac os x comes up with a message about unrecognized keyboard, and closes both PSM connections. (i was faking an apple keyboard which is risky when actually connecting to an apple computer i suppose. I need to work that out) without the reaoonse to the l2cap query, the virtual HID shows up on these devices as a keyboard, and after pairing the connection is stopped before ever opening psm channel 17 or 19 Thank you. > > > I did notice some clients request 0x1200 'pnp info' so I added > > SDP_SERVICE_CLASS_PNP_DEVICE handler to sdpd to see what would happen. > > The code is here -> https://github.com/waitman/sdpd/blob/master/pnp.c > > But the configuration parameters should be set by the request, not > > hardcoded into pnp.c (also hid.c should be fixed) > > The PNP Info can be useful, I use it for example (on NetBSD) to get the > product and vendor IDs in order to match a specific driver for the Apple > Magic Mouse, rather than the generic Bluetooth HID mouse driver. > > regards, > iain > _______________________________________________ > freebsd-bluetooth@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth > To unsubscribe, send any mail to " freebsd-bluetooth-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFuo_fyL-ZS6rBUR1bnLJ2m6ZoLoO=yq7JcY=AvhshNm=9uMqw>