From: Keith Bannister <keith.bannister@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Developing Broadcom driver support
Date: Tue, 7 Feb 2006 23:01:10 +0000 [thread overview]
Message-ID: <e44ae5e0602071501h650f1f1dl@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 349 bytes --]
Hi All,
I've struggled to follow all the discussion on the lack of information
coming from broadcom. Sourceforge forum seems difficult to drive.
I'd add that I'm happy to spend some time capturing the windows driver
behaviour with snoopyPRO (http://usbsnoop.sourceforge.net/) if that would
help.
Any takers?
K
--
Keith Bannister
[-- Attachment #2: Type: text/html, Size: 447 bytes --]
next reply other threads:[~2006-02-07 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 23:01 Keith Bannister [this message]
2006-02-08 0:55 ` [Bluez-devel] Developing Broadcom driver support Brad Midgley
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=e44ae5e0602071501h650f1f1dl@mail.gmail.com \
--to=keith.bannister@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;
as well as URLs for NNTP newsgroup(s).