From owner-freebsd-current Mon Apr 24 10:37:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7F50A37B5F1 for ; Mon, 24 Apr 2000 10:37:39 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA04458; Mon, 24 Apr 2000 10:36:41 -0700 Date: Mon, 24 Apr 2000 10:37:24 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: asm_pci.h,v Holy cow! In-Reply-To: <200004241726.NAA34251@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > This is probably an okay idea, except how would you include such files? > > I'm not sure I follow your naming scheme in /usr/firmware- what's wrong with > > /usr/src/sys/dev/firmware/{isp, esh, ...}? > > The fact that said directory is under CVS control, which is what I'm > suggesting we get away from. Umm, then I sure don't get what you're wanting to do. > > The files can be compiled into the kernel very easily using `file2c', > or simply loaded directly by the boot loader. > I put in maybe 40-80 hours testing per f/w upgrade. There has to be some assurance that what you load is correct. CVS does give some assurance of strong versioning. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message