From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco problems
Date: Tue, 02 Aug 2005 09:02:39 -0600 [thread overview]
Message-ID: <42EF8B0F.6020108@xmission.com> (raw)
In-Reply-To: <3967360605080206231820ee1f@mail.gmail.com>
Rob,
I believe CSR was the only chipmaker that was willing to give Marcel the
info he needed to implement SCO in the driver. You'll have to ask him.
I'm watching for a bt2.0 class 1 module :)
Brad
Robert Brewer wrote:
> Any thoughts on how hard it would be to make broadcom work?
> I'm willing to donate some time to help make it happen... I have
> some previous lower-level coding experience, but no bluetooth
> experience.
>
> Failing that, can anyone recommend a CSR dongle that is class 1 (100m range)
> and bluetooth 1.2?
>
> Thanks,
> Rob
>
> On 8/2/05, Brad Midgley <bmidgley@xmission.com> wrote:
>
>>Robert
>>
>>
>>>Zonet zub6101c usb dongle (class 1, bluetooth 1.2, broadcom chipset)
>>
>>I believe this is the problem. btsco can transfer audio only to CSR modules.
>>
>>Brad
>>
>
>
>
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-08-02 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 3:51 [Bluez-devel] btsco problems Robert Brewer
2005-08-02 4:15 ` Brad Midgley
2005-08-02 13:23 ` Robert Brewer
2005-08-02 15:02 ` Brad Midgley [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=42EF8B0F.6020108@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