From: Jeff Fern <sf@fcse.co.uk>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Multiple Headsets
Date: Mon, 10 Jan 2005 10:54:05 +0000 [thread overview]
Message-ID: <41E25ECD.2000505@fcse.co.uk> (raw)
Hello all,
I have sucessfully got Bluez and the bt-snd-sco alsa stuff working with
my debian 2.6.9 and mh5 patch.
What I would like to do is get two headsets working, as two seperate
audio devices so I can cat /dev/dsp1 to /dev/dsp2 and pass audio through.
Whenever I currently try and connect two headsets, the second one
reports the SCO channel is already in use.
I do have two bluetooth USB dongles that can be used (although would
like to just use one if possible).
I should point out that my background is in Java and not C, so although
I have examined the bt-snd-sco and btsco source files, I do not
understand them enough to be able to see what is going on.
Any help would be much appreciated,
Regards,
-Jeff Fern
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-01-10 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 10:54 Jeff Fern [this message]
2005-01-10 11:32 ` [Bluez-devel] Multiple Headsets Lars Grunewaldt
2005-01-10 13:02 ` Marcel Holtmann
2005-01-10 16:14 ` Lars Grunewaldt
2005-01-11 9:26 ` Brad Midgley
2005-01-11 10:15 ` Marcel Holtmann
2005-01-11 10:30 ` Lars Grunewaldt
2005-01-11 16:27 ` Brad Midgley
2005-01-11 16:37 ` Marcel Holtmann
2005-01-11 16:55 ` Lars Grunewaldt
2005-01-12 1:47 ` Lars Grunewaldt
2005-01-16 19:49 ` Jeff Fern
2005-01-16 20:41 ` Lars Grunewaldt
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=41E25ECD.2000505@fcse.co.uk \
--to=sf@fcse.co.uk \
--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