public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Becker <matthias.becker@beyondsoft.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH]Re:  multithreaded name resolution
Date: Thu, 11 Oct 2007 13:10:25 +0200	[thread overview]
Message-ID: <1192101025.8393.4.camel@matthias.BEYONDSOFT.local> (raw)
In-Reply-To: <20071001154023.53e57c49@localhost.localdomain>

> > > 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.
> > 
> > this won't work. Asking for the name of a device is some sort of 
> > connection setup, and most (all ?) Bt chips do not allow / can not handle 
> > parallel connection setups (even though parallel connections are 
> > possible). 
> > 
> > So don't try further, the problem is outside your code (and even BlueZ). 
> > 
> 
> That's not true, the reported behavior is produced by bluez-libs. I already
> sent a patch to fix it and will attach that patch again to this mail.
> 
> Please let me know if that Patch fixes your problem Matthias.
> 
> Greetings
> 
> Andy
> 
> See also:
> http://thread.gmane.org/gmane.linux.bluez.devel/12491

Sorry for the delay. I tried your patch and in my tests it works
perfectly with up to three parallel name requests using this bluetooth
adapter: http://www.trust.com/products/default.aspx?item=14693

Thanks

-- Matthias Becker


-------------------------------------------------------------------------
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

  parent reply	other threads:[~2007-10-11 11:10 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   ` [Bluez-devel] multithreaded name resolution Matthias Becker
2007-08-24 12:14     ` 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         ` Matthias Becker [this message]
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=1192101025.8393.4.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