From: Matthias Becker <matthias.becker@beyondsoft.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] multithreaded name resolution
Date: Fri, 24 Aug 2007 16:06:33 +0200 [thread overview]
Message-ID: <1187964393.5121.10.camel@matthias.BEYONDSOFT.local> (raw)
In-Reply-To: <8de6c3e20708231340j439ca230i487e816693149441@mail.gmail.com>
Hi,
I tried to read the name of different devices parallel using multi
threading, but without success. If there is one bluetooth device I works
(as there is no real multi threading). If there are who devices, the
same name is reported for both devices. In another test with 6 devices
hci_read_remote_name returned something <0 so I did not get any name at
all.
hcitool scan --flush
Scanning ...
00:1A:89:6F:DE:EE Nokia 5300
00:19:63:9D:09:16 K800i
My multithreaded tool:
00:19:63:9D:09:16 K800i
00:1A:89:6F:DE:EE K800i
When I don't start multiple threads but do it single threaded everything
works fine, and my code should be absolutly threadsafe.
Is this a bug in BlueZ or was it never supposed to work parallel?
When I run hcidump -V I see that the right names are recived:
> HCI Event: Remote Name Req Complete (0x07) plen 255
status 0x00 bdaddr 00:1A:89:6F:DE:EE name 'Nokia 5300'
> HCI Event: Remote Name Req Complete (0x07) plen 255
status 0x00 bdaddr 00:19:63:9D:09:16 name 'K800i'
-- Matthias
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-08-24 14:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 13:12 [Bluez-devel] Multiple Bluetooth Dongles Williams, Richard
2007-08-23 20:40 ` Jeffrey Cuenco
2007-08-24 12:13 ` Marcel Holtmann
2007-08-24 14:06 ` Matthias Becker [this message]
2007-08-24 12:14 ` [Bluez-devel] multithreaded name resolution Peter Wippich
2007-10-01 13:40 ` [Bluez-devel] [PATCH]Re: " Andreas Gaufer
2007-10-01 14:12 ` [Bluez-devel] Patch mh3 Olivier Le Pogam
2007-10-01 14:14 ` Marcel Holtmann
2007-10-01 14:50 ` Olivier Le Pogam
2007-10-01 15:56 ` Marcel Holtmann
2007-10-01 16:55 ` Mats Erik Andersson
2007-10-11 11:10 ` [Bluez-devel] [PATCH]Re: multithreaded name resolution Matthias Becker
2007-08-24 12:14 ` [Bluez-devel] Multiple Bluetooth Dongles Marcel Holtmann
2007-08-24 14:08 ` Williams, Richard
2007-08-24 14:25 ` Marcel Holtmann
2007-08-24 15:06 ` Williams, Richard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1187964393.5121.10.camel@matthias.BEYONDSOFT.local \
--to=matthias.becker@beyondsoft.de \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox