From owner-freebsd-arch@FreeBSD.ORG Wed May 14 20:36:33 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 389C937B401 for ; Wed, 14 May 2003 20:36:33 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EC0043F3F for ; Wed, 14 May 2003 20:36:32 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.9) with ESMTP id h4F3a9m2055228; Wed, 14 May 2003 20:36:09 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h4F3a9eX055227; Wed, 14 May 2003 20:36:09 -0700 (PDT) Date: Wed, 14 May 2003 20:36:08 -0700 From: "David O'Brien" To: Harti Brandt Message-ID: <20030515033608.GA55202@dragon.nuxi.com> Mail-Followup-To: David O'Brien , Harti Brandt , arch@freebsd.org References: <20030514172614.F737@beagle.fokus.fraunhofer.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030514172614.F737@beagle.fokus.fraunhofer.de> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: arch@freebsd.org Subject: Re: Where to place this firmware X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: arch@freebsd.org List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2003 03:36:33 -0000 On Wed, May 14, 2003 at 06:02:13PM +0200, Harti Brandt wrote: > 1) Put it into a kernel module that is loaded/unloaded during device > initialisation. Would this be possible (not from a technical point of > view, but from a legal one: would the copyright infect the kernel? Would > it be enough if the firmware itself lived in sys/contrib?) You could always make a port of it -- that would allow you to not deal with putting a binary file into CVS.