From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [RFC] : Bluez audio routing: introducing switch alsa plugin
Date: Mon, 11 Dec 2006 08:29:03 -0700 [thread overview]
Message-ID: <457D793F.6080504@xmission.com> (raw)
In-Reply-To: <457C2D1F.1050605@free.fr>
Fabien
> The idea is to bring in the picture a new plugin that i would call
> conveniently the 'switch' plugin.
> As its name suggests, its role would be to route to either one PCM
> stream or another PCM.
This approach would be ok I think. It's an implementation detail.
One motivation for this approach would be keeping a2dp and sco daemons
separate. Are you still interested in doing it that way?
We have been running with the assumption that we will have a single
daemon for sco and a2dp. So Connect(addr) would attempt to make control
connections for both protocols. Does this become too difficult?
Brad
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2006-12-11 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 15:51 [Bluez-devel] [RFC] : Bluez audio routing: introducing switch alsa plugin Fabien Chevalier
2006-12-11 15:29 ` Brad Midgley [this message]
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=457D793F.6080504@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