public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Johan van der Boom <Johan.vanderBoom@tomtom.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] not able to send SCO voice data
Date: Wed, 27 Oct 2004 11:20:39 +0200	[thread overview]
Message-ID: <1098868839.6611.18.camel@pegasus> (raw)
In-Reply-To: <F162D20C428AB34E9E4491C6CF5F8B9A02A1813B@posthoorn.intra.local>

Hi Johan,

> I'm trying to run the hstest and am unable to send any SCO voice data to
> the headset. Receiving SCO voice data from the headset works OK. After
> several successful writes to the SCO socket it returns an error. None of
> the successful writes have actually been transmitted over the HCI UART
> link.
> 
> hciconfig returns:
>   ACL MTU: 120:20  SCO MTU: 64:0
> 
> The 'hci read buffer size' command returns:
>   < HCI Command: Read Buffer Size (0x04|0x0005) plen 0
>   > HCI Event: Command Complete (0x0e) plen 11
>     01 05 10 00 78 00 00 14 00 00 00
> 
> What I think is happening, is that the BlueZ stack thinks the bluetooth
> device has not got any space to store any SCO packets since the 'hci
> read buffer size' command returns 0 for HC_Total_Num_SCO_Data_Packets
> and also 0 for HC_SCO_Data_Packet_Length, and therefore does not send
> any SCO data and at some point runs out of internal buffers and returns
> an error in the write to the SCO socket.
> 
> Is this assumption correct?, Or does the BlueZ stack interpret the 0
> HC_Total_Num_SCO_Data_Packets as meaning the bluetooth device does not
> support flow control as is intended by the bluetooth device, and
> something else goes wrong?

I don't think that this is the problem. Since you use an UART as host
transport you should try a voice setting of 0x0040 and modify the hstest
tool to use 8bit instead of 16bit.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-10-27  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27  7:25 [Bluez-devel] not able to send SCO voice data Johan van der Boom
2004-10-27  9:20 ` Marcel Holtmann [this message]
2004-10-27 12:45 ` [Bluez-devel] err corridge in sdp.c Paolino paperino
2004-10-27 13:01   ` Marcel Holtmann

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=1098868839.6611.18.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=Johan.vanderBoom@tomtom.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