From owner-freebsd-bluetooth@FreeBSD.ORG Tue Sep 13 18:16:45 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3D7D16A41F for ; Tue, 13 Sep 2005 18:16:45 +0000 (GMT) (envelope-from urnenfel@tiscali.es) Received: from smtp106.mail.sc5.yahoo.com (smtp106.mail.sc5.yahoo.com [66.163.169.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 7A52B43D46 for ; Tue, 13 Sep 2005 18:16:45 +0000 (GMT) (envelope-from urnenfel@tiscali.es) Received: (qmail 82934 invoked from network); 13 Sep 2005 18:16:44 -0000 Received: from unknown (HELO rdhome) (urnen81@80.102.195.75 with login) by smtp106.mail.sc5.yahoo.com with SMTP; 13 Sep 2005 18:16:43 -0000 Message-ID: <007e01c5b88f$4acf2250$0100a8c0@rdhome> From: "Oliver" To: "Maksim Yevmenkin" References: <002a01c5afc7$c31eb750$0100a8c0@rdhome> <431CB7E3.4000701@savvis.net> Date: Tue, 13 Sep 2005 20:16:37 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Cc: freebsd-bluetooth@freebsd.org Subject: Re: BCM2035 X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 18:16:45 -0000 Maksim Sorry for the delay of this thread. > i'm not aware of any hci command that would allow you to re/set bd_addr. > i'm interested to know what did you do to make it forget its bd_addr. Just casted normal commands, the initialitation ones, inquiry process, set auth / encrypt, get link keys and the maximun possible, write the class of device, i am suspecting of those last ones. Another of my suspects could be the casting of the RESET command before init process of the device... for this concrete chip... The device is working but as it identifies itself as a null BD_ADDR inquiry of other devices don't catch it, but is possible to work with in all other features/commands. And as I could see the replies to the post i did in the BlueZ stack maillist you can even work with it if you start the connection process.. As well I commented in the BlueZ maillist there is some info about how to set the BD_ADDR to an "Ericsson ROK 101" > HCI Command: ogf 0x3f, ocf 0x000d, plen 6 > HCI Command: ogf 0x3f, ocf 0x0022, plen 0 If I dont find any solution or info form broadcom i would start to cast commands in this range... but if it is a combination of more than 1 command it is quite impossible to get it. With only 1 command, more possibilities to end up with it than fixing but... Any advice, hint about this? > i'm afraid there is nothing on top of my head right now :( i will need to > have the device itself to run some tests. i will see if i can purchase it > locally and let you know. really really weird..... thanks a lot! ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es