linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Multiple headsets with one dongle
Date: Fri, 13 Jan 2006 10:10:16 -0700	[thread overview]
Message-ID: <43C7DEF8.4050007@xmission.com> (raw)
In-Reply-To: <43C6F96B.6080402@sonar-security.com>

Michael

> number, but what I haven't been able to get working is one headset
> calling the other. Well, actually, it *does* work, but the audio is
> totally unusable.
> 
> From what I have been able to gather so far, the headsets are using
> RFCOMM channel 2 (sdptool search --bdaddr 0x111E), and so when both are
> communicating with the dongle at the same time, they most likely are
> interfering each other. My questions are:

The rfcomm channel communication is not where interference happens. It's
when both headsets try to build the sco connection at the same time.

> 3. The dongle, configured as master, *should* support up to three slaves
> using the handsfree profile?

I'm not totally sure how to do this anyway. Marcel has hinted at it and
apparently there's a boot-time parameter to set something to allow two
sco connections. I tried to capture everything in the btsco bug for
multiple headsets, but this is all I come up with there:

Marcel adds: "To get more than one SCO channel working the hci_usb
driver must be fixed to dynamicaly change the alternate settting."

I think he was working on the generic case but if you know how many
headsets you have paired with you could set the alternate setting once
and leave it alone I think.

Brad


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-01-13 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13  0:50 [Bluez-devel] Multiple headsets with one dongle Michael Puchol
2006-01-13 17:10 ` Brad Midgley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-12 13:58 [Bluez-devel] AVDTP in BlueZ Martin Raspaud
2006-01-13 20:34 ` Brad Midgley
2006-01-13 22:54   ` [Bluez-devel] Multiple headsets with one dongle Southwing - Miquel Puchol

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=43C7DEF8.4050007@xmission.com \
    --to=bmidgley@xmission.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).