From: Tom K <tomk@runbox.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco not working with 3Com 3CREB96 and SE HBH-602
Date: Thu, 23 Mar 2006 17:25:50 +0000 [thread overview]
Message-ID: <4422DA1E.6030303@runbox.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603231619010.25910@cherokee.spacecom.si>
Mitja Pufic wrote:
> Hello,
>
> This is a very old dongle, with bluecore01 and confirms with bluetooth
> 1.0b specification. And as far as I know it has SCO mapped to PCM and not
> HCI, so this is the reason, why your setup is not working. Check mail
> list archive how to change this, or if it is even possible on this old
> chip. PCMCIA version does not have this problem.
>
>
Many thanks for your response.
It's pretty old alright, but hciconfig hci0 revision gives me
hci0: Type: USB
BD Address: 00:04:76:AD:12:E3 ACL MTU: 128:8 SCO MTU: 64:8
HCI 10.3
Chip version: BlueCore01b (ES)
SCO mapping: HCI
which looked promising to me. Still, if it's not the right stuff, I'll
hunt around for another one.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-03-23 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 11:23 [Bluez-devel] btsco not working with 3Com 3CREB96 and SE HBH-602 Tom K
2006-03-23 15:22 ` Mitja Pufic
2006-03-23 17:25 ` Tom K [this message]
2006-03-24 11:24 ` Mitja Pufic
2006-03-24 12:43 ` Tom K
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=4422DA1E.6030303@runbox.com \
--to=tomk@runbox.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.