From: "Carlos Azevedo" <carlosarazevedo@netcabo.pt>
To: <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Re: Re: Lifetech BlueConnect DOES NOT work with bluez
Date: Thu, 18 Nov 2004 14:50:29 -0000 [thread overview]
Message-ID: <000e01c4cd7d$f2c02020$2c00a8c0@DISCO17G> (raw)
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
Hi Marcel,
No, this dongle has a SiliconWave chipset. This chipset implements the 1.2 spec, but Bluez implements 1.1 only. Specifically, on the 1.2 spec the Add SCO Connection is deprecated and indicated as 'not to be used'. The Bluez code (net/bluetooth/hci_conn.c) uses that command to start a SCO voice connection to a headset. I'm suspecting that the dongle doesn't implement the Add SCO command properly and causes my problems. But nevertheless a 1.2 spec device is not required (and is even discoraged) to implement it.
The hcidump indicates that the connection is established but on shut down (when the SCO socket is closed) a first disconnect exchange is concluded but SCO data keeps coming in. The Bluez code complains about those packets (in hci_scodata_packet) and only after a second disconnect exchange does the SCO data stop.
I'm now trying to use the Create Synchronous Connection (as per 1.2 spec) instead to see if this works.
By the way hcidump 1.16 reports the Create command as an Accept one (0x01|0x0028).
Carlos A. R. Azevedo
[-- Attachment #2: Type: text/html, Size: 1706 bytes --]
next reply other threads:[~2004-11-18 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 14:50 Carlos Azevedo [this message]
2004-12-15 16:22 ` [Bluez-devel] Re: Re: Lifetech BlueConnect DOES NOT work with bluez 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='000e01c4cd7d$f2c02020$2c00a8c0@DISCO17G' \
--to=carlosarazevedo@netcabo.pt \
--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