Date: Tue, 17 Mar 2015 18:20:36 +0000 (GMT) From: Iain Hibbert <plunky@ogmig.net> To: Waitman Gobble <gobble.wa@gmail.com> Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org> Subject: Re: register HID with SDP error Message-ID: <alpine.NEB.2.11.1503171759510.4792@galant.ogmig.net> In-Reply-To: <CAFuo_fx47uRC-eKD_KtsSsrMCQZauyHyCOgRxGbtp_WEZ49o_Q@mail.gmail.com> References: <CAFuo_fy9xRU2T3GUPY8116yZCUd8sL9pBQ9ixXnMwO56niJFog@mail.gmail.com> <CAFuo_fzdmB79qdoH8P5EcO_ZZoa=_id6h=eqFBXvP_a%2B3WMkLw@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Mar 2015, Waitman Gobble wrote: > hcidump log https://gist.github.com/waitman/c3f8a3bc9b046e36dbb5 Kind of unrelatedly, from that log, the Linux machine requests a search for Protocol UUID 0x0100 (L2CAP) but gets nothing in return.. > ACL data: handle 0x0048 flags 0x02 dlen 24 L2CAP(d): cid 0x44 len 20 [psm 1] SDP SSA Req: tid 0x0 len 0xf pat uuid-16 0x0100 (L2CAP) max 0xffff aid(s) 0x0000 - 0xffff cont 00 < ACL data: handle 0x0048 flags 0x02 dlen 15 L2CAP(d): cid 0x40 len 11 [psm 1] SDP SSA Rsp: tid 0x0 len 0x6 cnt 0x3 cont 00 ..does the SDP server not return results for that, Max? Then, more pertinently the unexpected syntax is probably an artifact of your modifications, as hcidump should be able to parse anything legal. can you save the binary dump next time? (hcidump -w <file>) you can look at it with "hcidump -r <file>" but it might help to be able to examine the hex values, in the case where an unexpected syntax occurs.. 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. regards, iain
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.NEB.2.11.1503171759510.4792>