Date: Sat, 12 Nov 2005 09:55:41 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org, Brooks Davis <brooks@one-eyed-alien.net>, freebsd-rc@freebsd.org, "M. Warner Losh" <imp@bsdimp.com> Subject: Re: [RFC] rc.d integration for the bluetooth subsystem Message-ID: <20051112175541.GA18302@odin.ac.hmc.edu> In-Reply-To: <4375681B.6030808@savvis.net> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> <20051111.165103.110975378.imp@bsdimp.com> <20051112000929.GB10648@odin.ac.hmc.edu> <4375681B.6030808@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 11, 2005 at 07:57:15PM -0800, Maksim Yevmenkin wrote: > Brooks Davis wrote: >=20 > >On Fri, Nov 11, 2005 at 04:51:03PM -0700, M. Warner Losh wrote: > > > >>In message: <4375246E.3050303@savvis.net> > >> Maksim Yevmenkin <maksim.yevmenkin@savvis.net> writes: > >>: does anyone have any objections to the /etc/devd.conf patch located at > >>:=20 > >>: http://people.freebsd.org/~emax/devd.conf.diff.txt > >>:=20 > >>: this patch will add support for a usb bluetooth dongles to devd(8). > >> > >>That looks fine to me. >=20 > good. thanks for review. i have committed the patch. >=20 > >>: also while i'm here where do we stick firmware files by default? > >> > >>/usr/share seems most logical to me, but suffers from the 'can't load > >>firmware until after /usr is mounted' issue. For most firmware, this > >>is a minor issue... > > > >It's also not an issue in practice for most installations since /usr is > >local and gets mounted quite early. It's only when /usr is NFS and not > >part of / that you usually get into trouble. >=20 > let me just some more details. in this particular case i'm interested=20 > where to put firmware files for bluetooth devices. in particular >=20 > 1) 3com bluetooth pccard v1 >=20 > 2) broadcom bcm2033 chip based usb bluetooth devices (belkin, d-link, etc= .) >=20 > in both cases firmware files are _not_ loadable modules. they are just=20 > files in vendor specific format. tools are provided (bt3cfw(8) and=20 > bcmfw(8)) to load firmware into device. >=20 > what i would like to do is to add a couple more sections into the=20 > /etc/devd.conf to handle these devices. those sections can even be=20 > commented out because we cannot include firmware into the distribution.= =20 > it is up to the user to find firmware and put it in the right place. >=20 > so, should i create /usr/share/firmware directory or just use=20 > /usr/share? is it better to have common place for firmware files or have= =20 > each driver/tool define its own place? Instead, I would suggest creating a port that installs the firmware and a /usr/local/etc/devd/ script simliar to the iwi-firmware port. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --G4iJoqBmSsgzjUCe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDdiybXY6L6fI4GtQRAvKuAJ93GkaxQj4pXuHU2va1klVu3WilhwCfRhMT tAEEBXeVbodoNmEqVvw+Zw4= =Qu5e -----END PGP SIGNATURE----- --G4iJoqBmSsgzjUCe--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051112175541.GA18302>