Date: Fri, 28 Apr 2000 09:37:40 +1000 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: current@FreeBSD.ORG Subject: Re: asm_pci.h,v Holy cow! Message-ID: <00Apr28.093740est.115303@border.alcanet.com.au> In-Reply-To: <200004241726.NAA34251@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Tue, Apr 25, 2000 at 03:27:38AM %2B1000 References: <200004241536.LAA33905@khavrinen.lcs.mit.edu> <Pine.BSF.4.05.10004240905110.87419-100000@semuta.feral.com> <200004241726.NAA34251@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 25, 2000 at 03:27:38AM +1000, Garrett Wollman wrote: >The fact that said directory is under CVS control, which is what I'm >suggesting we get away from. How do you suggest such files get distributed? Everything else is in the CVS repository and most (if not all) of our build process is designed around it. As Matt pointed out, CVS provides us with a good mechanism for ensuring that I can identify what version of the firmware I am using - and be reasonably certain it matches the code that Matt (or whoever) validated. >The files can be compiled into the kernel very easily using `file2c', >or simply loaded directly by the boot loader. I don't see the purpose of having a firmware image permanently resident (especially given their sizes). Getting the boot loader to directly load the firmware into the device seems a much nicer solution. If this is impractical, treating the firmware as a kld and unloading it after downloading the firmware would seem the next best option. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00Apr28.093740est.115303>