From: David Greaves <david@dgreaves.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] 2 instances of btsco on one dongle...
Date: Fri, 09 Jun 2006 18:08:35 +0100 [thread overview]
Message-ID: <4489AB13.3020501@dgreaves.com> (raw)
Hi
I'm running btsco 0.42 happily with an HDW-3 headset and an Epox (CSR)
USB dongle on 2.6.16.9.
I'd like to be able to use 2 headsets with the same dongle. That should
work shouldn't it? (theoretically)
When I run a second btsco it just creates a new connection and
overwrites the old one. I was going to start hacking around the source
to see if I could make it work but I thought I'd check to see if it was
feasible or if I've misunderstood something.
David
--
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-06-09 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 17:08 David Greaves [this message]
2006-06-09 17:12 ` [Bluez-devel] 2 instances of btsco on one dongle Fabien Chevalier
2006-06-09 17:26 ` Brad Midgley
2006-06-09 17:45 ` Fabien Chevalier
2006-06-09 18:31 ` David Greaves
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=4489AB13.3020501@dgreaves.com \
--to=david@dgreaves.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;
as well as URLs for NNTP newsgroup(s).