public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: nirav rabara <niravrabara@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Bluetooth Dongle version mismatch Confusion
Date: Wed, 10 Mar 2010 15:14:03 +0530	[thread overview]
Message-ID: <912bb79a1003100144g7d14c3daj9560dc0ae0dc8e31@mail.gmail.com> (raw)

Hi,

I have been using bluez 4.58 with 2.6.30 on ARM platform , I am newbie
and found problem with Headset & Dongle version mismatch.

I can use v2.0 Dongle with v2.0 Headset & v2.1 Dongle with v2.1
Headset.( result is good I can hear voice on HS)

But if I use v2.0 Dongle with v2.1 HS & v2.1 Dongle with v2.0 HS
result is unpredictable some time noise or No voice).

I am doing anything wrong with SCO implementation? OR Bluetooth have
limitation with version mismatch. OR I must use same version Dongle &
HS(why ?).

Thanks in Advance


--
With Regards,
Nirav Rabara

             reply	other threads:[~2010-03-10  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  9:44 nirav rabara [this message]
2010-03-10 21:40 ` Bluetooth Dongle version mismatch Confusion Mike Tsai

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=912bb79a1003100144g7d14c3daj9560dc0ae0dc8e31@mail.gmail.com \
    --to=niravrabara@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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