Date: Mon, 14 Nov 2005 12:36:56 +0200 From: Panagiotis Astithas <past@ebs.gr> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org, "M. Warner Losh" <imp@bsdimp.com> Subject: Re: [RFC] rc.d integration for the bluetooth subsystem Message-ID: <437868C8.10508@ebs.gr> In-Reply-To: <437667D4.5030205@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> <20051112175541.GA18302@odin.ac.hmc.edu> <437667D4.5030205@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Maksim Yevmenkin wrote: > Brooks, > > [...] > >> Instead, I would suggest creating a port that installs the firmware >> and a /usr/local/etc/devd/ script simliar to the iwi-firmware port. > > > ok. that sounds fine to me. does anyone have experience with this like > this? i mean do i have to contact 3com and broadcom and obtain some sort > of permission for this? how does this work? > > linux bluez has rpm that contains firmware. it seems like they have > contacted broadcom, because they have firmware files in their cvs > > http://cvs.sourceforge.net/viewcvs.py/bluez/firmware/broadcom/ > > can i legally get those files and include them into freebsd port's > collection? if this is going to lead to too much corporate brouhaha then > perhaps i should leave it as it is. bcmfw(8) and bt3cfw(8) man pages > already tell users where they can get the firmware. You could just have the port fetch the files from sourceforge and avoid including any copyrighted material in the ports repository. Regards, Panagiotis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?437868C8.10508>