From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez/alsa modules vs kernel
Date: Thu, 14 Jun 2007 13:17:43 -0600 [thread overview]
Message-ID: <d89ddf300706141217q4c88eb74mc5b8b6de0592775c@mail.gmail.com> (raw)
In-Reply-To: <861055.97568.qm@web62305.mail.re1.yahoo.com>
[-- Attachment #1.1: Type: text/plain, Size: 430 bytes --]
walt
> Isn't there an alsa interface that can be used without patching?
> ie Do all applications that use alsa when it's in the kernel, patch?
I'm not sure what you're asking. Have you tried out plugz are you only
talking about btsco? Also which headset are you working with?
There is a recommended kernel patch regardless of which approach you use for
voice headsets. See plugz/patches for the sco-flowcontrol patch.
Brad
[-- Attachment #1.2: Type: text/html, Size: 663 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-06-14 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 14:10 [Bluez-users] bluez/alsa modules vs kernel walt shekrota
2007-06-13 4:46 ` Brad Midgley
2007-06-13 19:35 ` walt shekrota
2007-06-14 19:17 ` Brad Midgley [this message]
2007-06-16 19:51 ` walt shekrota
2007-06-17 0:42 ` Brad Midgley
2007-06-17 2:28 ` walt shekrota
2007-06-19 1:05 ` walt shekrota
2007-06-19 3:28 ` Brad Midgley
2007-06-19 14:16 ` walt shekrota
2007-06-19 14:21 ` walt shekrota
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=d89ddf300706141217q4c88eb74mc5b8b6de0592775c@mail.gmail.com \
--to=bmidgley@gmail.com \
--cc=bluez-users@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