From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluetooth Audio question
Date: Wed, 28 Mar 2007 14:48:39 -0600 [thread overview]
Message-ID: <460AD4A7.9050409@xmission.com> (raw)
In-Reply-To: <5FD5754DDBA0B1499B5A0B4BB5419485CD0D36@fmsmsx411.amr.corp.intel.com>
Mark
> I am assuming that no more work is done to maintain the btsco /
> snd-bt-sco
> infrastructure. Is this correct?
I will accept patches but I am not working on it.
> I looked at the notes on using plugz and sbc.
>
> I am a bit confused. You mention a kernel patch. Is this needed for
> using btsco or using plugz? I thought that by using all user space
> communication between the bluetooth and the Alsa, we don't have to worry
> about any kernel stuff. What is the kernel patch all about? My site uses
>
> the 2.6.17.13 kernel.
>
> Do any of you know if there are any issues using plugz with a bluetooth
> headset (for talking and listening with Skype) with Alsa 1.0.14rc3?
sadly, plugz does not have as many features as btsco, such as generating
rings in the headset. The daemon inside bluez-utils is being done right
so it can handle this but it's not ready for the desktop case yet.
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
next prev parent reply other threads:[~2007-03-28 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 20:30 [Bluez-devel] Bluetooth Audio question Allyn, Mark A
2007-03-28 20:48 ` Brad Midgley [this message]
2007-03-28 21:16 ` Allyn, Mark A
2007-03-28 21:17 ` Allyn, Mark A
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=460AD4A7.9050409@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.