From owner-freebsd-current Mon Apr 24 11:44: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id A53BC37B666 for ; Mon, 24 Apr 2000 11:43:58 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Mon, 24 Apr 2000 13:43:45 -0500 From: Richard Wackerbarth To: Julian Elischer Subject: Re: asm_pci.h,v Holy cow! Date: Mon, 24 Apr 2000 13:43:44 -0500 X-Mailer: KMail [version 1.1.41] Content-Type: text/plain Cc: current@FreeBSD.ORG References: <39041698.15FB7483@elischer.org> <200004241536.LAA33905@khavrinen.lcs.mit.edu> <39046BF1.1CFBAE39@elischer.org> In-Reply-To: <39046BF1.1CFBAE39@elischer.org> MIME-Version: 1.0 Message-Id: <00042413373504.09404@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Apr 2000, Julian Elischer wrote: > This seems well thought out and I certainly agree that we don't need > DIFFs of firmware. > I wonder if we can somehow "cheat time" and get that 13MB file out of > the source tree and retro-actively tag the new scheme so > that we don't have to carry it around forever :-) It looks like a port, Smells like a port, and tastes like a port. It must be a ..... merlot ? Seriously, perhaps we should consider putting optional pieces of the kernel (eventually much of it, I hope) into a ports style structure. This structure can already take care of most of the problems like this one because it has multiple mechanisms whereas the source tree has only one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message