Linux bluetooth development
 help / color / mirror / Atom feed
From: Sergey Smirnov <svs1957@gmail.com>
To: Mayank BATRA <mayank.batra@st.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco: Operation not supported
Date: Wed, 11 Apr 2007 11:48:28 +0400	[thread overview]
Message-ID: <461C92CC.9060300@gmail.com> (raw)
In-Reply-To: <004501c77c0b$dc64da70$9d0cc70a@dlh.st.com>

I have the same problem with bluez-utils 3.7
Then I compile version 3.9.
I think that problem in hcid.
I can stop it only by kill -9

I have Socket CF BT card on PDA. I'll try to find information is it support SCO.
Thanks

Mayank BATRA wrote:
>> Here hciconfig -a
>> hci0:   Type: PCCARD
>>         BD Address: 00:E0:03:25:7C:36 ACL MTU: 340:4 SCO MTU: 0:0
>>         UP RUNNING PSCAN ISCAN
>>         RX bytes:204 acl:0 sco:0 events:15 errors:0
>>         TX bytes:382 acl:0 sco:0 commands:15 errors:0
>>         Features: 0xbf 0x00 0x20 0x00 0x00 0x00 0x00 0x00
>>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
>>         Link policy: RSWITCH HOLD SNIFF PARK
>>         Link mode: SLAVE ACCEPT
>>         Name: 'svs-zaurus-0'
>>         Class: 0x3e0100
>>         Service Classes: Networking, Rendering, Capturing, 
>> Object Transfer, Audio
>>         Device Class: Computer, Uncategorized
>>         HCI Ver: 1.1 (0x1) HCI Rev: 0x0 LMP Ver: 1.1 (0x1) 
>> LMP Subver: 0x21a
>>         Manufacturer: Nokia Mobile Phones (1)
> 
> It took me a while to understand this confusing situation.
> 
> The reason for this behaviour is very simple.
> Have a look at the Features of your device: 0xbf 0x00 0x20 0x00 0x00
> 0x00 0x00 0x00
> Here, byte 0 is 0xbf, byte 1 is 0x00. If you decode these numbers from
> the bluetooth specs, bit 3 of byte 1 stands for SCO link. In your case
> it is 0 which means your device does not support SCO links at all. Get
> yourself a new dongle :(
> Now you would ask me why does the packet type shows HV1? This is because
> HV1 is mandatory if the device supports SCO link. So this is just a
> mistake done by hciconfig. It should report HV1 packet type only if SCO
> link bit is 1. In case it is 0 do not mention HV1.
> 
> Hope this helps.
> 
> Best Regards,
> 
> Mayank
> 
> 


-------------------------------------------------------------------------
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

  reply	other threads:[~2007-04-11  7:48 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
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 [this message]
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=461C92CC.9060300@gmail.com \
    --to=svs1957@gmail.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=mayank.batra@st.com \
    /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