alsa-lib plugin for bluetooth

[Brad Midgley <bmidgley@xmission.com>]

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]

Hi

I am working on the bluetooth-alsa project.

I want to try moving our code out of kernel space and I've looked at the 
jack plugin. It's a little confusing.

Is there a blow-by-blow somewhere to explain how to get asound 
configured and running with the jack plugin?

To start with, I will create a plugin that consumes writes and produces 
a square wave when it's read. I'll start working on the bluetooth stuff 
once I'm happy with that.

Does the card,dev,subdev device description map well to bluetooth? Would 
it be bluetooth-adapter,headset,service or something like that?

I've been digging in the api docs and I've attached my first patch. :)

Brad

[-- Attachment #2: three-bytes --]
[-- Type: text/plain, Size: 742 bytes --]

diff -u alsa-lib-1.0.6-orig/src/pcm/pcm.c alsa-lib-1.0.6/src/pcm/pcm.c
--- alsa-lib-1.0.6-orig/src/pcm/pcm.c   2004-05-04 09:13:23.000000000 -0600
+++ alsa-lib-1.0.6/src/pcm/pcm.c        2004-11-29 14:25:31.000000000 -0700
@@ -206,7 +206,7 @@

 The full list of formats present the #snd_pcm_format_t type.
 The 24-bit linear samples uses 32-bit physical space, but the sample is
-stored in low three bits. Some hardware does not support processing of full
+stored in low three bytes. Some hardware does not support processing of full
 range, thus you may get the significant bits for linear samples via
 #snd_pcm_hw_params_get_sbits() function. The example: ICE1712
 chips support 32-bit sample processing, but low byte is ignored (playback)