From owner-freebsd-rc@FreeBSD.ORG  Mon Nov 14 10:37:28 2005
Return-Path: <owner-freebsd-rc@FreeBSD.ORG>
X-Original-To: freebsd-rc@freebsd.org
Delivered-To: freebsd-rc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 02E4816A41F;
	Mon, 14 Nov 2005 10:37:28 +0000 (GMT) (envelope-from past@ebs.gr)
Received: from fly.ebs.gr (fly.ebs.gr [62.103.84.177])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0AD6443D45;
	Mon, 14 Nov 2005 10:37:26 +0000 (GMT) (envelope-from past@ebs.gr)
Received: from ebs.gr (root@hal.ebs.gr [10.1.1.2])
	by fly.ebs.gr (8.12.9p1/8.12.9) with ESMTP id jAEAb79V058295;
	Mon, 14 Nov 2005 12:37:07 +0200 (EET) (envelope-from past@ebs.gr)
Received: from [10.1.1.158] (pc158.ebs.gr [10.1.1.158])
	by ebs.gr (8.13.3/8.12.11) with ESMTP id jAEAbE69048965;
	Mon, 14 Nov 2005 12:37:18 +0200 (EET) (envelope-from past@ebs.gr)
Message-ID: <437868C8.10508@ebs.gr>
Date: Mon, 14 Nov 2005 12:36:56 +0200
From: Panagiotis Astithas <past@ebs.gr>
Organization: EBS Ltd.
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051106)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Maksim Yevmenkin <maksim.yevmenkin@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>
In-Reply-To: <437667D4.5030205@savvis.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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
X-BeenThere: freebsd-rc@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion related to /etc/rc.d design and implementation."
	<freebsd-rc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-rc>,
	<mailto:freebsd-rc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-rc>
List-Post: <mailto:freebsd-rc@freebsd.org>
List-Help: <mailto:freebsd-rc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-rc>,
	<mailto:freebsd-rc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2005 10:37:28 -0000

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