From: Marcel Holtmann <marcel@holtmann.org>
To: gonzalo briceno <gonzalohbriceno@yahoo.com>
Cc: Luiz Fernando Capitulino <lcapitulino@conectiva.com.br>,
bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Key step in bluetonium setup, bcm203x does not load firmware
Date: Mon, 06 Sep 2004 10:24:13 +0200 [thread overview]
Message-ID: <1094459053.5145.9.camel@notepaq> (raw)
In-Reply-To: <20040905073705.47183.qmail@web52803.mail.yahoo.com>
Hi Gonzalo,
> You are completely right. I followed your instructions and my
> Broadcom Bluetonium (bcm203x module) based chip is working. I hope I
> did not gloss over any section of information although I am almost
> positive that I did not. Anyways, any one having this problem has to
> simply download bluez-firmware and copy the broadcom files onto
> /usr/lib/hotplug/firmware.
the /usr/lib/hotplug/firmware was the old place for firmware files and
we came to the conclusion that putting them into /lib/firmware is much
better. The Debian Sarge/Sid and the upcoming SuSE 9.2 support both
directories, so it is a problem of the hotplug package of your
distribution.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-09-06 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 14:11 [Bluez-users] Key step in bluetonium setup, bcm203x does not load firmware gonzalo briceno
2004-09-02 17:29 ` Luiz Fernando Capitulino
2004-09-05 7:37 ` gonzalo briceno
2004-09-06 8:24 ` Marcel Holtmann [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=1094459053.5145.9.camel@notepaq \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=gonzalohbriceno@yahoo.com \
--cc=lcapitulino@conectiva.com.br \
/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.