From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 14 17:18:07 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C74BB16A420; Mon, 14 Nov 2005 17:18:07 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 326E043D46; Mon, 14 Nov 2005 17:18:07 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jAEHI1Hk005487; Mon, 14 Nov 2005 09:18:01 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jAEHI0Of005486; Mon, 14 Nov 2005 09:18:00 -0800 Date: Mon, 14 Nov 2005 09:18:00 -0800 From: Brooks Davis To: Panagiotis Astithas Message-ID: <20051114171800.GA1928@odin.ac.hmc.edu> 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> <437868C8.10508@ebs.gr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <437868C8.10508@ebs.gr> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: Brooks Davis , freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org, "M. Warner Losh" Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 17:18:07 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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= =20 > >this? i mean do i have to contact 3com and broadcom and obtain some sort= =20 > >of permission for this? how does this work? > > > >linux bluez has rpm that contains firmware. it seems like they have=20 > >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=20 > >collection? if this is going to lead to too much corporate brouhaha then= =20 > >perhaps i should leave it as it is. bcmfw(8) and bt3cfw(8) man pages=20 > >already tell users where they can get the firmware. >=20 > You could just have the port fetch the files from sourceforge and avoid= =20 > 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 --=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 --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDeMbHXY6L6fI4GtQRAqlxAJ0dqYkSpwbwp3RKzj52c/1mkixWagCgg0wM 0HfW8FcwIOgWIELWE1TTsZk= =xnXP -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--