From owner-freebsd-bluetooth@FreeBSD.ORG Mon Mar 16 20:41:16 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 E16E2C4E for ; Mon, 16 Mar 2015 20:41:16 +0000 (UTC) Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e: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 A1B5E8E for ; Mon, 16 Mar 2015 20:41:16 +0000 (UTC) Received: by pabyw6 with SMTP id yw6so75131992pab.2 for ; Mon, 16 Mar 2015 13:41:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=o/Hy0nHKIo5nhODKFn/l1SMHRCMmcLnrdVKmBcPHcDQ=; b=RVnaFTbOhfyMnXZmJT8TkM5yZCBqU2ddD9G6RK+jSkmbEpfqXFY+WXhfHZnOiZGD2p jf5phtDufyMXt3m0IEHFA6/TDRddyFZUlBtJ/X1gy8+72R8m4Z0XDfQ0CBrTqgo8EdGV owDfi5hECA3/9VyaG/QgWBqNRqALpM2+gcTFVAfmq+pUL0nTdGv6pm37eJKAZ/YSi7FE 48w0UD1IKBWDSFhPrB+Wmk51a8XUUJOEz/4+zyr2XIKHk3jVPoO+QeKEQskXuLn8j5G+ 0Lp1ss9wCO77YsJCFNk8NLsM13p6zJ4ngMgqMMhExGxPNLzkuyLVmt7pqzPbFMJJrggr XsKQ== X-Received: by 10.66.63.106 with SMTP id f10mr141944667pas.0.1426538476197; Mon, 16 Mar 2015 13:41:16 -0700 (PDT) Received: from [10.71.137.194] ([128.177.161.177]) by mx.google.com with ESMTPSA id nj5sm18742661pdb.24.2015.03.16.13.41.15 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Mar 2015 13:41:15 -0700 (PDT) References: Mime-Version: 1.0 (1.0) In-Reply-To: Message-Id: <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com> X-Mailer: iPhone Mail (12D508) From: maksim yevmenkin Subject: Re: register HID with SDP error Date: Mon, 16 Mar 2015 13:41:13 -0700 To: Waitman Gobble Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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, 16 Mar 2015 20:41:17 -0000 > Thanks, that helps alot. >=20 > I am also working on my other issue, the bluetooth stack not starting. The= example in the manual shows the same vendor CSR but product 0x0001, I belie= ve all my bt devices are 0x0002. It seems that the bluetooth stack will fail= if it does not identify the device.. so I'm tracking down where to add it..= this device is actually functioning even without the bluetooth stack starti= ng. >=20 Device vendor and product id pair should not matter too much. The driver mak= es the match based on usb interface class and subclass. If device is fully c= onfirms to the spec then it usually just works.=20 Some devices (Atheros and Broadcom for example) may require some sort of fir= mware download. I've also seen all sort of weirdness in devices usually requ= iring special driver or shim.=20 In most cases, if ng_ubt(4) driver attaches to the device, then it should wo= rk. If yo get usb transfer errors then I would suspect usb. I've seen this b= efore. Also what version of FreeBSD are you running this on ? Thanks Max=