From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] AGC and anti-noise patch for btsco kernel module
Date: Mon, 22 Aug 2005 16:10:39 -0600 [thread overview]
Message-ID: <430A4D5F.7090201@xmission.com> (raw)
In-Reply-To: <20050822185341.GA18549@uni-duesseldorf.de>
Andreas,
The adaptive strategy you chose seems like it will work well. That was
very quick coding and good intuition on the noise problem! I'll try the
patch.
Converting our kernel module to an alsa userspace driver is on the
roadmap and I believe your approach could be used there as well.
Marcel will probably ask why we don't fix the problem in the bluez
layers if that's where it is, so every SCO app benefits.
Can you surround the adaptive stuff and swapping stuff with two
different macros so we can select them independently? Like USE_ADAPTIVE
and USE_AUTOSWAP or something?
Brad
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-08-22 22:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 19:38 [Bluez-devel] btsco - a few comments and a small .py script Andreas Beck
2005-08-19 20:44 ` John Gruenenfelder
2005-08-20 20:13 ` Brad Midgley
2005-08-21 12:12 ` Andreas Beck
2005-08-21 19:26 ` Andreas Beck
2005-08-22 4:29 ` Brad Midgley
2005-08-22 12:09 ` Andreas Beck
2005-08-22 18:38 ` Andreas Beck
2005-08-22 18:53 ` [Bluez-devel] AGC and anti-noise patch for btsco kernel module Andreas Beck
2005-08-22 22:10 ` Brad Midgley [this message]
2005-08-23 15:04 ` Andreas Beck
2005-08-23 16:05 ` Andreas Beck
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=430A4D5F.7090201@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.