Linux bluetooth development
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: jp-www@dcs.gla.ac.uk
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [ANNOUNCE] ALSA Bluetooth Headset Driver
Date: Mon, 15 Sep 2003 15:30:53 +0100	[thread overview]
Message-ID: <3F65CD1D.1020100@superbug.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.54.999.0309150112530.29667@sibu.dcs.gla.ac.uk>

jp-www@dcs.gla.ac.uk wrote:
> Hi,
> 
> Having recently got a Bluetooth headset (HBH-60), I've put together a
> preliminary ALSA driver which works with bluez.
> 
> 	http://www.dcs.gla.ac.uk/~jp/snd-bluez-sco/
> 
> I'd appreciate any feedback on this. The code is a bit messy at the
> moment, but I've had fairly good results with it.
> 
> No changes to bluez are required at the moment -- all the work is done
> through the SCO socket interface. Better performance could likely be
> obtained with a slightly different interface.
> 
> This is a work-in-progress -- no guarantees that it will work!
> 
> 
> An excerpt from the small README file:
> 
> ALSA Bluetooth Headset Driver
> =============================
> 
> This is a preliminary driver for Bluetooth headsets. It has only been
> tested with the following configurations:
> 
>     USB Bluetooth adapter (Bluecore02 and 01b)
>     usb-ohci, usb-uhci and uhci driver (on a desktop and laptop)
>     kernel 2.4.20 single processor (there may be race conditions)
>     alsa-0.9.6
>     HBH-60 Bluetooth headset
>     recent bluez, hci_usb with my extra patches for SCO support (hciusb-isoc.patch)
> 
> Only 8-bit (8000hz) mode is supported at the moment. You must configure
> your hci device with 'hciconfig hci0 voice 0x0040'.
> 
> The speaker and microphone volume levels are presented as ALSA mixer
> controls. The HBH-60 only supports speaker volume, so I haven't managed
> to test the microphone support.
> 
> The ALSA device doesn't produce or consume any audio data when the headset
> isn't connected via the bluezsco control program -- this will cause apps
> to time out after a few seconds.
> 
> Pressing the headset button while connected will disconnect. Pressing the
> headset button while disconnected (assuming the headset decides to connect
> to your PC rather than your phone) will not work, since the control
> program doesn't (yet) act as a server.
> 
> Please get in touch if you manage to get it to work or have any questions.
> 

I was also working on this. Do you have full duplex sound working ?
I was under the impression that changes needed to be made to the 
bluetooth stack before full duplex worked.

Cheers
James





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2003-09-15 14:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15  0:21 [Bluez-devel] [ANNOUNCE] ALSA Bluetooth Headset Driver jp-www
2003-09-15 14:30 ` James Courtier-Dutton [this message]
2003-09-15 14:51   ` jp-www
2003-09-26  8:51 ` Sjoerd Simons
2003-09-26  8:59   ` Jonathan Paisley
2003-09-26  9:59     ` Sjoerd Simons

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=3F65CD1D.1020100@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=jp-www@dcs.gla.ac.uk \
    /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