Date: Tue, 26 Feb 2008 15:39:06 -0800 From: "Kip Macy" <kip.macy@gmail.com> To: "Sam Leffler" <sam@errno.com> Cc: cvs-src@freebsd.org, cvs-all@freebsd.org, src-committers@freebsd.org, Kip Macy <kmacy@freebsd.org>, John Baldwin <jhb@freebsd.org> Subject: Re: cvs commit: src/sys/dev/cxgb bin2h.pl cxgb_main.c cxgb_t3fw.c cxgb_t3fw.h t3fw-5.0.0.bin.gz.uu src/sys/modules/cxgb Makefile src/sys/modules/cxgb/cxgb Makefile src/sys/modules/cxgb/cxgb_t3fw Makefile src/sys/conf NOTES files Message-ID: <b1fa29170802261539t697dfc58l3f4788476514cfa8@mail.gmail.com> In-Reply-To: <47C4A083.2050602@errno.com> References: <200802260302.m1Q32KOT081487@repoman.freebsd.org> <200802261133.00942.jhb@freebsd.org> <b1fa29170802261507v5b336f36mcdab9bae65869e0a@mail.gmail.com> <b1fa29170802261519y7940b16em7c26e3175831ff14@mail.gmail.com> <47C4A083.2050602@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <sam@errno.com> 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 <kip.macy@gmail.com> wrote: > >> On Tue, Feb 26, 2008 at 8:33 AM, John Baldwin <jhb@freebsd.org> 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. > >> > > > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170802261539t697dfc58l3f4788476514cfa8>