public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Brewer <rwb123@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] broadcom SCO questions
Date: Wed, 3 Aug 2005 15:19:57 -0400	[thread overview]
Message-ID: <396736060508031219119970cf@mail.gmail.com> (raw)

This is mainly directed at Marcel...

As the proud owner of a new Broadcom-based
dongle, I'd really like to get it working with btsco.

Brad had mentioned that only CSR chipsets are
supported for SCO right now.  I'm interested
in taking up the charge and would like to know
what has been tried already so I don't repeat=20
it.

Is the thinking that the broadcom chip needs some special
commands to enable SCO?  Has broadcom been
contacted and refused to provide details?  Has
reverse engineering of the Windows USB traffic
been attempted?

I looked at the Bluetooth H:2 spec for USB=20
and it seemed pretty light on details.  I also
looked at the broadcom-specific bluez driver code
and it seemed to be for uploading firmware and
causing the dongle to reattach as a standard H:2
device.

I've recently "rediscovered" my WinXP partition
on my laptop, so I may try to test the Windows
driver that came with my dongle and see if I can
get the headset working.

Thanks for any info.

-Rob
--=20
Robert W. Brewer


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

                 reply	other threads:[~2005-08-03 19:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=396736060508031219119970cf@mail.gmail.com \
    --to=rwb123@gmail.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