From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [Bluez-devel] Remote name delay From: Marcel Holtmann To: bluez-devel@lists.sourceforge.net In-Reply-To: References: <1133470780.18554.2.camel@blade> Content-Type: text/plain Message-Id: <1133523028.20834.8.camel@blade> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 02 Dec 2005 12:30:28 +0100 Hi Claudio, > > > I am developing a standalone application to perform real D-Bus > > > services tests. The main features are: > > > 1. Running all the time in the systray > > > 2. Handle PIN Request > > > 3. Local adapter configuration > > > 4. Basic operations: Inquiry, Remote name, ... > > > > cool idea. We really need something like this. > > I am not a good UI developer, but this application can be the start > point for other developers to improve it. I will sent the first > prototype to the list as soon as I get better icons :) is this for Gnome and in C? I like to create a bluez-gnome repository and then make a pre-release really soon. > > > However I am facing a problem in the RemoteName service when a lot of > > > inquiry replies is received. My app stores the inquired devices in a > > > hash table and when the InquiryCompleted signal is received the app > > > request the name for each device. The "hci_send_req" function is > > > returning an Input/Output error. Looking the hcidump result, the > > > "Command Disallowed" error is displayed :( > > > > > > HCIDUMP: > > > > HCI Event: Command Status (0x0f) plen 4 > > > Remote Name Request (0x01|0x0019) status 0x0c ncmd 1 > > > Error: Command Disallowed > > > <<<< > > this command at this time.>>>> > > > > > > I noticed the same problem using the hcitool with "--flush" option and > > > removing the cached device information stored in the directory > > > "/var/lib/bluetooth". > > > > What kind of chip is in your dongle? Do you wait until the remote name > > complete event before asking for the next name? Every name request needs > > at least a partial baseband connection. > > Dongle - D-Link DBT-122 > Class: 0x3e0100 > Service Classes: Networking, Rendering, Capturing > Device Class: Computer, Uncategorized > HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x309 > Manufacturer: Broadcom Corporation (15) > > Yes, I am waiting for the RemoteNameComplete signal, for this case it > works fine. But I am testing simultaneous request. BlueZ D-Bus client > developers should not care about listen for RemoteNameComplete event > before send another request. We can try define a queue for > simultaneous request. What do you think? What are the other > operations that we will find the same problem? You will always see this problem if the establishment of baseband connection is needed, meaning if you create an ACL link. The good thing is that extended inquiry will solve this almost, but for older devices the only possibility is to retrieve the name from a cache or queue the commands. > I will submit a patch to improve the remote name in order to consider > the clock offset and page scan parameters. Don't expose these commands over the D-Bus interface. We don't wanna deal with them there, because they should be internal only. Regards Marcel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel