From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] 2 instances of btsco on one dongle...
Date: Fri, 09 Jun 2006 11:26:51 -0600 [thread overview]
Message-ID: <4489AF5B.7060303@xmission.com> (raw)
In-Reply-To: <4489AC19.3030200@free.fr>
Fabien
> I don't know if btsco can handle more than one headset, however what is
> sure is that the hci USB driver cannot (as SCO support is not complete...)
> Having what you want to work might require quite a lot of work actually :-(
starting with the plugin-alsa-sco would be less work than modifying
btsco and its kernel mod. then we only have to deal with the sco part.
but then maybe that's what you were thinking of when you say it's a lot
of work.
brad
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-09 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 17:08 [Bluez-devel] 2 instances of btsco on one dongle David Greaves
2006-06-09 17:12 ` Fabien Chevalier
2006-06-09 17:26 ` Brad Midgley [this message]
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=4489AF5B.7060303@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;
as well as URLs for NNTP newsgroup(s).