From: Sergey Smirnov <svs1957@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] btsco: Operation not supported
Date: Tue, 10 Apr 2007 16:25:38 +0400 [thread overview]
Message-ID: <461B8242.1090800@gmail.com> (raw)
In-Reply-To: <461B7E3A.4030008@sportlaan.adsl.utwente.nl>
Thank you for answer.
I'm sure that modules loaded:
svs-zaurus:~# lsmod|grep sco
sco 11396 0
snd_bt_sco 13868 2
snd_hwdep 7620 2 snd_bt_sco
snd_pcm 84613 8 snd_bt_sco,snd_soc_pxa2xx,snd_soc_core,snd_pxa2xx_ac97,snd_ac97_codec,snd_pxa2xx_pcm,snd_pcm_oss
snd_page_alloc 6600 2 snd_bt_sco,snd_pcm
snd 53876 18 snd_bt_sco,snd_hwdep,snd_soc_corgi,snd_soc_wm8731,snd_soc_core,snd_pxa2xx_ac97,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
bluetooth 52736 10 sco,rfcomm,l2cap,dtl1_cs
svs-zaurus:~#
Also I'm sure that devices was paired.
I check /var/lib/bluetooth/<BT_ADDR>
And also I can cat > /dev/rfcomm[0|1] which is tty of headset
Here is some part of hcidump while sco connect:
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 1 packets 1
> HCI Event: Command Status (0x0f) plen 4
Add SCO Connection (0x01|0x0007) status 0x11 ncmd 4
Error: Unsupported Feature or Parameter Value
> ACL data: handle 1 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 2
Berend Dekens wrote:
> Make sure you have sco support in your kernel, as a module or compiled
> in. Don't forget to load the module..
>
> FYI: I have my share of trouble with SCO audio links so I have no clue
> what else you can do :)
>
> Berend
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-04-10 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 8:44 [Bluez-devel] btsco: Operation not supported Sergey Smirnov
2007-04-10 12:08 ` Berend Dekens
2007-04-10 12:25 ` Sergey Smirnov [this message]
2007-04-11 4:39 ` Mayank BATRA
2007-04-11 6:34 ` Sergey Smirnov
2007-04-11 6:41 ` Mayank BATRA
2007-04-11 6:53 ` Sergey Smirnov
2007-04-11 7:32 ` Sergey Smirnov
2007-04-11 7:40 ` Mayank BATRA
2007-04-11 8:28 ` Sergey Smirnov
2007-04-11 9:38 ` Sergey Smirnov
2007-04-11 9:41 ` Mayank BATRA
2007-04-11 7:34 ` Mayank BATRA
2007-04-11 7:48 ` Sergey Smirnov
2007-04-10 13:28 ` Sergey Smirnov
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=461B8242.1090800@gmail.com \
--to=svs1957@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.