From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Re: Lifetech BlueConnect DOES NOT work with bluez
Date: Wed, 15 Dec 2004 17:22:26 +0100 [thread overview]
Message-ID: <1103127746.8717.11.camel@pegasus> (raw)
In-Reply-To: <000e01c4cd7d$f2c02020$2c00a8c0@DISCO17G>
Hi Carlos,
for what is the blue background good? This is a mailing list and not a
beauty contest ;)
> 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.
Now we are talking about SCO support? You complained that your dongle is
not working at all.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-12-15 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 14:50 [Bluez-devel] Re: Re: Lifetech BlueConnect DOES NOT work with bluez Carlos Azevedo
2004-12-15 16:22 ` Marcel Holtmann [this message]
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=1103127746.8717.11.camel@pegasus \
--to=marcel@holtmann.org \
--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