On Tue, Mar 17, 2015 at 11:20 AM, Iain Hibbert <[email protected]> wrote: > 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?
well, i don't think i ever got around to adding a feature that looks for uuid inside records. it currently only matches service class uuid's. so, yes, query for l2cap uuid will return nothing currently. its trivial to add this though. i think i even have a patch somewhere. [...] > 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 thanks, max _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[email protected]"
