From owner-freebsd-bluetooth@FreeBSD.ORG Sat Mar 21 15:20:02 2015 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 11A4092A for ; Sat, 21 Mar 2015 15:20:02 +0000 (UTC) Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com [IPv6:2a00:1450:400c:c00::235]) (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 801EE162 for ; Sat, 21 Mar 2015 15:20:01 +0000 (UTC) Received: by wgra20 with SMTP id a20so112070046wgr.3 for ; Sat, 21 Mar 2015 08:19:59 -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:content-transfer-encoding; bh=wyxhrXwssarmCWMULx7UbjKC98ZjE2NfwADbaQ4L1dE=; b=xwusJJtGowtHqkbRP8DUc2Y1v2dVHS1uPs+gcy7fxgSbJs9M36tHXGD7XIj36MwjrO ifOQ3TJ7MsESt7LJFF91WTotJck7fcEmxltv7Qd2iMUCn9yr3n9s9nWtC5HBKhjONuPt 6za0qsRIgdGdNxvp/J2SSyHGqettHLH9Bxexpl4qoZbhimL4JnjEjyA+Ledf6tcIb5aB 7KULr9zpy7hiE2jGx3NRpJDWI6Oc3u+jG0Di57KeKz12dx9/tFSoD/3g/b0CD7xL+PpQ BF/DUZVrrFH+blhtGWoCtR9Z43tEGrbDAVflmDIEAyk18caCjLYl5FG40SMlbQ8HvDAF uyUQ== MIME-Version: 1.0 X-Received: by 10.180.23.106 with SMTP id l10mr5174335wif.54.1426951199934; Sat, 21 Mar 2015 08:19:59 -0700 (PDT) Received: by 10.27.214.136 with HTTP; Sat, 21 Mar 2015 08:19:59 -0700 (PDT) In-Reply-To: <77352B43-637C-4E0D-B4CC-B42D977551F6@gmail.com> References: <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com> <77352B43-637C-4E0D-B4CC-B42D977551F6@gmail.com> Date: Sat, 21 Mar 2015 08:19:59 -0700 Message-ID: Subject: Re: register HID with SDP error From: Waitman Gobble To: maksim yevmenkin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-bluetooth@freebsd.org" , Iain Hibbert 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: Sat, 21 Mar 2015 15:20:02 -0000 On Sat, Mar 21, 2015 at 7:55 AM, maksim yevmenkin wrote: > > Hello! > >> Yes, thank you Max, that helps alot. >> >> One question, where is "Class" set? I believe this is causing me trouble > > You can set device class via hcicontrol. There is a command to do it. You= can also use configuration option that is going to be set when device atta= ches. Please take a look at /etc/rc.d/Bluetooth and how it starts things. Y= ou can create per-device configuration file that will set class, name etc. > > Thanks > Max > Hey, that works! Thank you. hccontrol Write_Class_Of_Device 02:50:40 so now I have to figure out how to send the PIN that the connecting device demands to receive. I suppose it's sending 0000. But it appears there has to be a human action in this case. < HCI Command: Accept Connection Request(0x01|0x0009) plen 7 > HCI Event: Command Status(0x0f) plen 4 > HCI Event: Role Change(0x12) plen 8 > HCI Event: PIN Code Request(0x16) plen 6 < HCI Command: PIN Code Request Reply(0x01|0x000d) plen 23 > HCI Event: Command Complete(0x0e) plen 10 > HCI Event: Connect Complete(0x03) plen 11 --=20 Waitman Gobble Los Altos California USA 510-830-7975