Linux bluetooth development
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Creating more than one instance of BlueZ
Date: Fri, 20 May 2005 08:10:56 -0600	[thread overview]
Message-ID: <428DEFF0.3050101@xmission.com> (raw)
In-Reply-To: <20050520075738.73600.qmail@web8308.mail.in.yahoo.com>

Mayank,

if you run "hciconfig" with two adapters connected, you see both hci0 
and hci1. you also see their bdaddrs.

iirc, when you create a bt socket we usually set "any" as the source 
(remember setting local_addr with bacpy(&local_addr, BDADDR_ANY) in 
a2recv.c). you can use a specific adapter and that is what you have to 
do when you have two adapters and you want to go out on a specific one.

when you connect to a service, obviously you can specify the bdaddress 
to connect to.

most of the core bluez code will allow you to set the src address using 
command-line arguments (a good example is -i <hciX|bdaddr> in hidd) but 
we've been lazy in the btsco code about that.

brad

Mayank Batra wrote:
> Brad,
> 
> 
>>I think the best you can expect is for bluez to see
>>hci0 and hci1. then 
>>you've got to make sure your apps choose the right
>>adapter.
>>
>>
> 
> 
> That is not possible since we have only one set of
> modules for l2cap, rfcomm, bnep etc.
> 
> So even if I tell my app to use which adapter, only
> one app will have exclusive access to the modules.
> And the other app will be waiting for the first app to
> free the modules.
> 
> A deadlock!
> 
> Mayank
> 
> ________________________________________________________________________
> Yahoo! India Matrimony: Find your life partner online
> Go to: http://yahoo.shaadi.com/india-matrimony
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2005-05-20 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20  7:57 [Bluez-devel] Creating more than one instance of BlueZ Mayank Batra
2005-05-20  8:17 ` Marcel Holtmann
2005-05-20 14:10 ` Brad Midgley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-19 12:06 Mayank Batra
2005-05-19 12:56 ` Brad Midgley
2005-05-19 13:06 ` Marcel Holtmann
2005-05-15 12:33 Mayank Batra

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=428DEFF0.3050101@xmission.com \
    --to=bmidgley@xmission.com \
    --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