From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 20:04:08 2005 Return-Path: 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 EF11E16A4CE for ; Thu, 6 Jan 2005 20:04:07 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7439B43D1F for ; Thu, 6 Jan 2005 20:04:07 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])j06K3YTt023186; Thu, 6 Jan 2005 14:03:34 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 14:03:25 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 14:03:10 -0600 Message-ID: <41DD997C.90605@savvis.net> Date: Thu, 06 Jan 2005 12:03:08 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ronald Klop References: <41DD82CE.5080502@savvis.net> <41DD9095.6010409@savvis.net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Jan 2005 20:03:11.0028 (UTC) FILETIME=[BF67EF40:01C4F42A] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2005 20:04:08 -0000 Ronald, >>> I commented out this list of hci-commands one by one and they all >>> give the same error. (Status: Command disallowed [0xc]) >>> reset >>> write_scan_enable 3 >>> write_class_of_device >>> change_local_name >> >> none of the commands above is strictly required. well, maybe with >> exception of 'write_scan_enable 3' command. this command supposed to >> make bluetooth device answer inquiry from the remote devices, i.e. it >> makes bluetooth device 'visible' to other devices. >> >> what is the output of >> >> % hccontrol -n ubt0hci read_node_state > > State: 0x3 ok, hci node is initialized >> % hccontrol -n ubt0hci read_scan_enable > > Status: Command disallowed [0xc] bummer :( >> % hccontrol -n ubt0hci read_class_of_device > > Status: Command disallowed [0xc] double bummer :( >> % hccontrol -n ubt0hci read_local_name > > Status: Command disallowed [0xc] triple bummer :( >> the output above looks fine, so i'd say it should work. >> >> - did you enable bluetooth on your phone? > > Yes, I did. Would be a nice mistake. :-) good. >> - did you make your phone 'visible' to other bluetooth devices (look >> somewhere under bluetooth security settings) > > Yes, I did. fine, just checking :) >> - what is your phone make and model? > > Sony Ericsson K700i that phone should work just fine. > I do not have other bluetooth devices to test with. > > And if I ask my phone to search for bluetooth devices it doesn't find > anything. yes, most (all) devices will not answer inquiry by default. that is what write_scan_enable command does. > I already read quite a lot about it and I think the not working > write_scan_enable is not good. correct. > Can you tell me what 'Status: Command disallowed [0xc]' means? i've never seen this before. but my guess would be it means exactly what it says: device has received command and decided that it does not want to execute it. > Is this my bluetooth adapter telling I can't issue the command, is it usb? its adapter. after the command is received the adapter will send hci event back. one of the fields is a status byte. non-zero status means something is wrong. > Or is it in the software (driver)? no, its adapter. > Or do you have any other clue about it? the spec on the web says this adapter is a bluetooth v1.2 adapter. i do not think it matters (there were no big changes since v1.1 - not in the hci commands/events at least). will look anyway. unless i get this specimen into my lab for dissection there is not much i can do. sorry :( max