[RFC] rc.d integration for the bluetooth subsystem

[Brooks Davis]

On Mon, Nov 14, 2005 at 12:36:56PM +0200, Panagiotis Astithas wrote:
> 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.

Yes.  Just make sure to set the RESTRICTED variable to cause the
distfiles and packages to not be distributed.  I'd suggest starting with
the net/ipw-firmware port (it's a little overly complex as it's the
master port for net/iwi-firmware, but it's got the basics.)

-- Brooks

-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-bluetooth/attachments/20051114/b30631e0/attachment.bin