From: Marcel Holtmann <marcel@holtmann.org>
To: Nosve <nosve@libero.it>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] New bc203x driver
Date: Thu, 08 Jan 2004 18:28:15 +0100 [thread overview]
Message-ID: <1073582894.2563.11.camel@pegasus> (raw)
In-Reply-To: <AGELIJDLJNOPFNMOHHIFAECHCAAA.nosve@libero.it>
Hi,
> excuse the easy questions but i never use usb devices with linux and
> hotplug; how it is intended to use the bcm203x driver? Has the firmware to
> be put in some particular location?
my setup has it this way
/etc/hotplug/firmware.agent
/usr/lib/hotplug/firmware/BCM2033-MD.hex
/usr/lib/hotplug/firmware/BCM2033-FW.bin
> Also, the hotplug configuration which started the bluefw program has to be
> removed? And how?
Check /etc/hotplug/usb.usermap or /etc/hotplug/usb/* for the bluefw
entry.
> Am I missing some documentation? Or I'm i the wrong place? :-)
The place is right, but I haven't written any documentation about this
new driver. I only wrote this driver for myself and made it public.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-01-08 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AGELIJDLJNOPFNMOHHIFKECGCAAA.nosve@libero.it>
2004-01-08 13:10 ` [Bluez-users] New bc203x driver (forget previous email with wrong subject :-) Nosve
2004-01-08 17:28 ` 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=1073582894.2563.11.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=nosve@libero.it \
/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