From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] a2dp, sco and kernel version
Date: Mon, 30 Jul 2007 18:26:25 -0600 [thread overview]
Message-ID: <d89ddf300707301726s6e657773td9e83a9dfd6b271d@mail.gmail.com> (raw)
In-Reply-To: <46AE7340.4010603@gmail.com>
Manuel
> Finally I compiled snd-bt-sco in my original kernel (2.6.17-13mdv) and I
> got sco working. But with a very low quality of audio. So my question
> is... How should I update my kernel?
sco is fairly low quality in the best circumstances, but it shouldn't
be choppy or unintelligible for voice.
brad
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-07-31 0:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 23:24 [Bluez-devel] a2dp, sco and kernel version Manuel Naranjo
2007-07-31 0:26 ` Brad Midgley [this message]
2007-07-31 0:34 ` Manuel Naranjo
2007-07-31 8:31 ` Frederic Dalleau
2007-07-31 8:52 ` Frederic Dalleau
2007-07-31 11:19 ` Manuel Naranjo
2007-07-31 16:29 ` Luiz Augusto von Dentz
2007-07-31 18:22 ` Manuel Naranjo
2007-08-01 7:38 ` Frederic Dalleau
2007-08-01 12:44 ` Manuel Naranjo
2007-08-02 3:22 ` Luiz Augusto von Dentz
2007-08-02 4:02 ` Manuel Naranjo
2007-08-02 13:04 ` Frederic Dalleau
2007-08-02 13:05 ` Frederic Dalleau
2007-08-02 15:18 ` Manuel Naranjo
2007-08-02 18:53 ` [Bluez-devel] a2dp, sco and kernel version [Possible Solution] Manuel Naranjo
2007-08-02 19:12 ` Brad Midgley
2007-08-02 19:24 ` Manuel Naranjo
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=d89ddf300707301726s6e657773td9e83a9dfd6b271d@mail.gmail.com \
--to=bmidgley@gmail.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