Linux bluetooth development
 help / color / mirror / Atom feed
From: "Cozza" <ac2crp@blueyonder.co.uk>
To: "Marcel Holtmann" <marcel@rvs.uni-bielefeld.de>,
	"James Courtier-Dutton" <James@superbug.demon.co.uk>
Cc: "bluez Dev" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluetooth headset problems.
Date: Tue, 8 Jul 2003 10:13:14 +0100	[thread overview]
Message-ID: <004101c34531$42d0a570$fd02a8c0@troll> (raw)
In-Reply-To: 1057529783.6946.88.camel@pegasus

Hi,

Sorry for not replying earlier!

I managed to get a TDK Bluetooth PC Card working successfully for both
record and playback with the headset.

This has a Bluecore chip too - I used the same hstest code and the same
kernel code. For this reason I suspect that the problem is with the USB
driver. Everything was the same in the working and non working versions,
except the PC card worked and the USB didn't. There was a minor variation in
the Bluecore firmware on the cards, but the USB device works successfully
under windows, so I don't think this is the issue.

If you like, you could mail me your modified driver and I'll see if I have
any luck recording with it. I have a working headset and code, so that might
be one less unknown if that is any use.

The 'running out of urb' problem you found sounds feasible. I printed out
the USB spec but have never quite got around to reading it yet :-(

Incidentally, the TDK Bluetooth card doesn't work with bluez by default - I
ended up patching the Linux PCMCIA Serial driver (serial_cs.o) in order to
make it work with Bluez. Once it has recognised the card, just treat the
card as a BCSP based device on the appropriate serial port using hciattach.

I shall investigate how to send a patch for the serial_cs driver and then
support for this card can be added into the latest Kernel.

Regards,

Colin

> > Question: Has anyone got a bluetooth headset working with the hstest
> > bluez tool and playing sound out of the headset speakers ?
> > I just want to double check that this is just a usb problem still.

  reply	other threads:[~2003-07-08  9:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 13:18 [Bluez-devel] Bluetooth headset problems James Courtier-Dutton
2003-07-03 11:05 ` Cozza
2003-07-03 12:36   ` James Courtier-Dutton
2003-07-05  1:55   ` James Courtier-Dutton
2003-07-06 18:59     ` James Courtier-Dutton
2003-07-06 20:44       ` Marcel Holtmann
2003-07-06 22:11         ` James Courtier-Dutton
2003-07-06 22:16           ` Marcel Holtmann
2003-07-08  9:13             ` Cozza [this message]
2003-07-09 10:06               ` David Woodhouse
2003-07-21 22:30       ` Max Krasnyansky

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='004101c34531$42d0a570$fd02a8c0@troll' \
    --to=ac2crp@blueyonder.co.uk \
    --cc=James@superbug.demon.co.uk \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@rvs.uni-bielefeld.de \
    /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