Linux bluetooth development
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] SCO packet for unknown connection handle
Date: Sun, 12 Nov 2006 21:39:29 -0500	[thread overview]
Message-ID: <20061113023929.GA8765@dominikbrodowski.de> (raw)

Hi!

I'm trying to get this dongle

hci0:	Type: USB
	BD Address: <hidden> ACL MTU: 120:20 SCO MTU: 0:0
	UP RUNNING PSCAN ISCAN 
	RX bytes:393 acl:0 sco:0 events:18 errors:0
	TX bytes:322 acl:0 sco:0 commands:18 errors:0
	Features: 0xff 0xff 0x05 0x38 0x18 0x18 0x00 0x00
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH HOLD SNIFF PARK 
	Link mode: SLAVE ACCEPT 
	Name: 'BlueZ (0)'
	Class: 0x3e0100
	Service Classes: Networking, Rendering, Capturing
	Device Class: Computer, Uncategorized
	HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x757
	Manufacturer: Silicon Wave (11)

to work using the bt sco alsa-plugin.

As the SCO MUT is reported to be 0:0 at first, I re-set it to 64:8 using

# hciconfig hci0 scomtu 64:8

Running

# /usr/bin/headsetd -n

looks promising, though playing sound using "aplay -D pcm.headset" does not
work:

headsetd[8300]: Bluetooth headset daemon version 0.42
headsetd[8300]: Incoming RFCOMM hs connection from <address> accepted
Headset connected
headsetd[8300]: Changing state: Idle-->Connected
headsetd[8300]: Changing state: Connected-->Ready
headsetd[8300]: unable to open bluetooth SCO socket
headsetd[8300]: Changing state: Ready-->Connected
Received from HS: AT+VGS=10

asound reports:
DEBUG: _snd_pcm_sco_open: Starting pcm_sco plugin.
DEBUG: _snd_pcm_sco_open: Open mode is for Playback.
aplay: main:550: audio open error: Operation now in progress

The kernel is Linus' latest 2.6.19-rc5, and it reports

[ 1845.813000] Bluetooth: RFCOMM socket layer initialized
[ 1845.814000] Bluetooth: RFCOMM TTY layer initialized
[ 1845.814000] Bluetooth: RFCOMM ver 1.8
... possible recursive locking warning snipped ...
[ 1898.408000] hci_scodata_packet: hci0 SCO packet for unknown connection handle 256

Running hciconfig afterwards has only these changes:
-	RX bytes:9824 acl:19 sco:167 events:57 errors:0
-	TX bytes:719 acl:17 sco:0 commands:29 errors:0
+	RX bytes:5044 acl:18 sco:9 events:92 errors:0
+	TX bytes:827 acl:17 sco:0 commands:65 errors:0

so no SCO TX... quite some time later the following appears in dmesg:

[ 2033.376000] hci_cmd_task: hci0 command tx timeout

Any ideas?

Thanks,
	Dominik

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2006-11-13  2:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13  2:39 Dominik Brodowski [this message]
2006-11-13  3:59 ` [Bluez-devel] SCO packet for unknown connection handle Brad Midgley
2006-11-13  8:39 ` Fabien Chevalier
2006-11-13 15:08   ` Brad Midgley

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=20061113023929.GA8765@dominikbrodowski.de \
    --to=linux@dominikbrodowski.net \
    --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