From: Stefan Seyfried <seife@suse.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Input service and multiple adapters
Date: Mon, 26 Mar 2007 09:06:53 +0200 [thread overview]
Message-ID: <20070326070653.GG32603@suse.de> (raw)
In-Reply-To: <200703252035.05891.dgollub@suse.de>
On Sun, Mar 25, 2007 at 08:35:05PM +0200, Daniel Gollub wrote:
> Hi folks,
>
> i started playing around with the Input DBUS API and found an obscurity when
> multiple bluetooth adapters are used. Actually this is a really rare use
> case...
>
> If i use Adapter A and call CreateDevice() and Connect() to an input device ..
> everything works as expected. If Adapter A got unplugged/broken and got
> replaced by Adapter B and call CreateDevice() for the same input device. The
> result will be org.bluez.input.AlreadyExists
>
> Again.. this is a really rare use case, but is it intended to only have one
No, it is pretty common.
I have one USB cable at home, with a hub and everything (including BT dongles)
connected to it and one USB cable at work, again with a BT dongle. And then i
have a BT dongle in my pocket for on-the-road usage.
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-03-26 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 18:35 [Bluez-devel] Input service and multiple adapters Daniel Gollub
2007-03-26 7:06 ` Stefan Seyfried [this message]
2007-03-27 16:42 ` Daniel Gollub
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=20070326070653.GG32603@suse.de \
--to=seife@suse.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