From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Creating more than one instance of BlueZ
Date: Fri, 20 May 2005 10:17:22 +0200 [thread overview]
Message-ID: <1116577042.24921.63.camel@pegasus> (raw)
In-Reply-To: <20050520075738.73600.qmail@web8308.mail.in.yahoo.com>
Hi Mayank,
> > 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!
this is simply wrong. No application will ever have exclusive access to
a kernel module. Or do you have to wait for your HTTP connection while
you are doing SMTP?
Regards
Marcel
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-05-20 8:17 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 [this message]
2005-05-20 14:10 ` Brad Midgley
-- 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=1116577042.24921.63.camel@pegasus \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.