public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Mr Jie Liu <s4048156@student.uq.edu.au>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] problem with hstest
Date: Tue, 18 May 2004 12:10:50 +0200	[thread overview]
Message-ID: <1084875050.5833.84.camel@pegasus> (raw)
In-Reply-To: <2260c2221e01.221e012260c2@uq.edu.au>

Hi,

>   I am using Anycom's USB 220 and it is not based on CSR chip. Here is the device information of it on my computer:
> [root@tom sbin]# ./hciconfig hci0 version
> hci0:   Type: USB
>         BD Address: 00:0B:0D:21:9E:81 ACL MTU: 339:4  SCO MTU: 64:0
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x93 LMP Ver: 1.1 (0x1) LMP Subver: 0x93
>         Manufacturer: Transilica, Inc. (24)
> [root@tom sbin]# ./hciconfig hci0 features
> hci0:   Type: USB
>         BD Address: 00:0B:0D:21:9E:81 ACL MTU: 339:4  SCO MTU: 64:0
>         Features: 0xff 0xff 0x3d 0x00
>                 <3-slot packets> <5-slot packets> <encryption> <slot offset>
>                 <timing accuracy> <role switch> <hold mode> <sniff mode>
>                 <park mode> <RSSI> <channel quality> <SCO link>
>                 <HV2 packets> <HV3 packets> <u-law log> <A-law log>
>                 <CVSD> <power control> <transparent SCO>
> [root@tom sbin]# ./hciconfig hci0 revision
> hci0:   Type: USB
>         BD Address: 00:0B:0D:21:9E:81 ACL MTU: 339:4  SCO MTU: 64:0
>         Unsupported manufacturer
> 
> Is there any other way I could figure out if the sco packets are routed through HCI or PCM interface? Can I trace it by hcidump?

I don't have any detailed information about the Transilica chip. Run
"hcidump -x" as root and if you see SCO packets then this dongles routes
the SCO data over HCI, otherwise it goes over the PCM.

And btw. do you activated the HCIUSB_SCO kernel option and do this
dongle really have the needed ISOC interface? You must check the content
of /proc/bus/usb/devices.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-05-18 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 10:00 [Bluez-devel] problem with hstest Mr Jie Liu
2004-05-18 10:10 ` Marcel Holtmann [this message]
2004-05-20 10:05   ` cuanyu
  -- strict thread matches above, loose matches on Subject: below --
2004-05-18  9:33 Mr Jie Liu
2004-05-18  9:39 ` 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=1084875050.5833.84.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=s4048156@student.uq.edu.au \
    /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