Uhm - I do the same thing as ispfw - can you tell me what is wrong with that?
-Kip On Tue, Feb 26, 2008 at 3:28 PM, Sam Leffler <[EMAIL PROTECTED]> wrote: > Huh? What does "static linking" mean? If you're looking for an example > of a firmware image being embedded in a kernel look at the npe firmware > used by xscale. > > Sam > > > > Kip Macy wrote: > > the make system doesn't work with firmware + static linking - this > > works around that > > > > > > On Tue, Feb 26, 2008 at 3:07 PM, Kip Macy <[EMAIL PROTECTED]> wrote: > >> On Tue, Feb 26, 2008 at 8:33 AM, John Baldwin <[EMAIL PROTECTED]> wrote: > >> > On Monday 25 February 2008 10:02:20 pm Kip Macy wrote: > >> > > kmacy 2008-02-26 03:02:20 UTC > >> > > > >> > > FreeBSD src repository > >> > > > >> > > Modified files: > >> > > sys/dev/cxgb cxgb_main.c > >> > > sys/modules/cxgb Makefile > >> > > sys/modules/cxgb/cxgb Makefile > >> > > sys/conf NOTES files > >> > > Added files: > >> > > sys/dev/cxgb bin2h.pl cxgb_t3fw.c cxgb_t3fw.h > >> > > sys/modules/cxgb/cxgb_t3fw Makefile > >> > > Removed files: > >> > > sys/dev/cxgb t3fw-5.0.0.bin.gz.uu > >> > > Log: > >> > > Move firmware in to separate module that can be compiled > statically in to > >> > the kernel > >> > > Add utility for converting future firmware revs to a C header file > >> > > >> > Did you consider using firmware(9)? It already handles wrapping a > binary blob > >> > into a kernel module for you and can autoload the firmware on demand. > >> > > >> > >> > >> Read the code. > >> > > > > > > _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
