From owner-freebsd-bluetooth@FreeBSD.ORG Mon Mar 23 07:25:50 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 A443141E for ; Mon, 23 Mar 2015 07:25:50 +0000 (UTC) Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) (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 2547DADE for ; Mon, 23 Mar 2015 07:25:50 +0000 (UTC) Received: by wegp1 with SMTP id p1so130187627weg.1 for ; Mon, 23 Mar 2015 00:25:48 -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=hcOKYri2xX4XfQOGiCBuYHZ9RJI4cFHpLy6vgC1MZt4=; b=oSOYNLbn7Kd/qOzbEbkyKxt4jIuXwUuH5R3xTR50V6+Muf3TaECbkT8f/u5y8kaAV0 3BREjGarKCG5WhZ652rVnNV7OTtA356F99s3uytxjlw3uc/tH1mzbe9oqYwyuOQjDeVf zG7IFVNGbLbxub8Ch4g8LyDdjqbrJp5Nxcr9rgwWHKgL1JsiCfD55Qa3hIIqBniE6dMZ JorHijDNhPkoobCkRE78U8wPdlUhnDhawDWVFVouEcc5T3nCnHsgorKlGag7FvwXo6rv sueKtTzSiM4HKr3aG5zUPShRf5LTVkzLqZrahxfSvBJizgV4I5v+hNtKTJzM9SYC3fC0 BIWw== MIME-Version: 1.0 X-Received: by 10.195.12.97 with SMTP id ep1mr185988230wjd.134.1427095548593; Mon, 23 Mar 2015 00:25:48 -0700 (PDT) Received: by 10.27.91.75 with HTTP; Mon, 23 Mar 2015 00:25:48 -0700 (PDT) Received: by 10.27.91.75 with HTTP; Mon, 23 Mar 2015 00:25:48 -0700 (PDT) In-Reply-To: References: <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com> Date: Mon, 23 Mar 2015 00:25:48 -0700 Message-ID: Subject: Re: register HID with SDP error From: Waitman Gobble To: Iain Hibbert Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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: Mon, 23 Mar 2015 07:25:50 -0000 On Mar 23, 2015 12:06 AM, "Iain Hibbert" 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"