public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: multi rfcomm/sco connection
Date: Wed, 10 Nov 2004 01:52:07 +0100	[thread overview]
Message-ID: <1100047927.25879.1.camel@pegasus> (raw)
In-Reply-To: <20041109144107.19373.qmail@webmail.aruba.it>

Hi,

> I was looking, few months ago, for a way to solve a problem more or less 
> like your. 
> 
> All what I could do was to set the headphones to HV3 and the bt-dongle too, 
> in this mode it was possible to "listen"  audio on 3 different channels, the 
> problem, for me, was that this channels were "mixed" so if with a channel I 
> was receiving 24bit with 3 channels they were 72, but I could not find a way 
> to "demux" this caos who was coming out, but I remember I found a way to 
> "create" 3 different sco connections with just one bt-(usb)-dongle.

this sounds like a problem with the wrong alternate setting on the ISOC
interface of the USB device. Your workaround is not reliable and maybe
it is CSR specific. To get more than one SCO channel working the hci_usb
driver must be fixed to dynamicaly change the alternate settting.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel/listinfo/bluez-devel

  reply	other threads:[~2004-11-10  0:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27 14:56 [Bluez-devel] SCO audio sync ubaldo
2004-07-27 15:06 ` Marcel Holtmann
2004-11-09 14:41   ` [Bluez-devel] Re: multi rfcomm/sco connection ubaldo
2004-11-10  0:52     ` Marcel Holtmann [this message]
2004-11-10 12:08   ` siemens s55 ubaldo
2004-11-10 14:05     ` [Bluez-devel] " Brad Midgley
2004-11-11 11:44   ` [Bluez-devel] " ubaldo
     [not found] <20041110041405.3CC331D4758@sc8-sf-uberspam1.sourceforge.net>
2004-11-14  4:30 ` [Bluez-devel] Re: multi rfcomm/sco connection Suriyan
2004-11-14 15:35   ` Marcel Holtmann
2004-11-14 16:16     ` Lars Grunewaldt
2004-11-14 16:34       ` Marcel Holtmann
     [not found] <E1CQIAu-0004AO-Dd@sc8-sf-list2.sourceforge.net>
2004-11-06 13:14 ` Suriyan
2004-11-06 13:50   ` Marcel Holtmann
2004-11-06 16:47     ` Lars Grunewaldt
  -- strict thread matches above, loose matches on Subject: below --
2004-06-18 17:54 [Bluez-devel] " ubaldo
2004-06-18 18:15 ` Marcel Holtmann
2004-06-18 18:33   ` ubaldo
2004-06-18 18:37     ` [Bluez-devel] " Marcel Holtmann
2004-06-18 18:42       ` ubaldo
2004-06-18 18:49         ` [Bluez-devel] " Marcel Holtmann
2004-07-16 14:02           ` ubaldo
2004-07-16 15:29             ` [Bluez-devel] " Marcel Holtmann
2004-08-04 22:45               ` Radha Thiagarajan
2004-08-04 23:35                 ` Marcel Holtmann
2004-08-05 15:33                   ` Radha Thiagarajan
2004-08-05 17:25                     ` 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=1100047927.25879.1.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