From owner-freebsd-bluetooth@FreeBSD.ORG Tue Mar 17 18:33:24 2015 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0141B2EB for ; Tue, 17 Mar 2015 18:33:23 +0000 (UTC) Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B06A76BC for ; Tue, 17 Mar 2015 18:33:23 +0000 (UTC) Received: by iecvj10 with SMTP id vj10so18993073iec.0 for ; Tue, 17 Mar 2015 11:33:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zi9j8w+jOe/O8455J2E7mLxmrC7hAOQ1sLgl62VhzsM=; b=DmrbaXmIBpaNyI7O8LDgp9IZ7Qx5vsYwvtBlVkMyeLP9QWjVarc5vEI+QJUfxJlipa DoeobiSBgQ1KsiOwokq9ofhQlcE5m59OV/Qwu/8FfKNmH6Fwfg29KDTDMY+BjydTkR0w 8a4JDDUhEraWGGVWIXAeOaLm8zsbuUBauQM0gY/JJuVOtPzEYwoXXMGEwHO4SrR5IPma FkbZXQv1eML8xf72ES9mxtx12nVQ4Q9ilqbVmjTdnngdYiprZA58gQiP886CP4C7k3lc KZCUwt/xt9PBeSmMwHvd986POy4KCmOjHwj+XU3ZRSkkoAPPrnokAt0a8PPcNkB3bleV 2VOA== MIME-Version: 1.0 X-Received: by 10.50.56.82 with SMTP id y18mr177648igp.25.1426617203127; Tue, 17 Mar 2015 11:33:23 -0700 (PDT) Received: by 10.36.66.74 with HTTP; Tue, 17 Mar 2015 11:33:23 -0700 (PDT) In-Reply-To: References: <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com> Date: Tue, 17 Mar 2015 11:33:23 -0700 Message-ID: Subject: Re: register HID with SDP error From: Maksim Yevmenkin To: Iain Hibbert Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-bluetooth@freebsd.org" X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2015 18:33:24 -0000 On Tue, Mar 17, 2015 at 11:20 AM, Iain Hibbert 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