From: Paul Webster <pjwebster@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Broadcom BCM2035 Firmware
Date: Mon, 15 Aug 2005 01:41:30 +1000 [thread overview]
Message-ID: <dc98d8d905081408412d2c43b5@mail.gmail.com> (raw)
Hi,
I have a laptop with a built in BCM2035 USB bluetooth module
("plugged" and "unplugged" by way of a "wireless" button). Downloaded
and installed the latest bluez packages from source, including the
firmware one. I notice that it only has BCM2033 firmware, and I'm
fairly sure this is being loaded when I modprobe the bcm203x kernel
module, however utilities all report BD Address as 00:00:00:00:00:00
regardless of whether the interface is up or down. Aside from this, it
all works ok, except that I have to specify the device (hci0) with
each tool command. I assume this is because they "use the first
available hci device by default", but because mine has a null address,
it isn't recognised.
Therefore, I have 2 questions:
Is there anywhere I can get 2035 firmware from? Can it be extracted
from the windows drivers, and if so, how?
Thanks
Paul W
-------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-08-14 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 15:41 Paul Webster [this message]
2005-08-16 15:37 ` [Bluez-users] Broadcom BCM2035 Firmware Marcel Holtmann
2005-08-18 12:13 ` Paul Webster
2005-08-19 14:46 ` 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=dc98d8d905081408412d2c43b5@mail.gmail.com \
--to=pjwebster@gmail.com \
--cc=bluez-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.