Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Feb 2008 15:28:03 -0800
From:      Sam Leffler <sam@errno.com>
To:        Kip Macy <kip.macy@gmail.com>
Cc:        cvs-all@FreeBSD.org, cvs-src@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:  <47C4A083.2050602@errno.com>
In-Reply-To: <b1fa29170802261519y7940b16em7c26e3175831ff14@mail.gmail.com>
References:  <200802260302.m1Q32KOT081487@repoman.freebsd.org>	 <200802261133.00942.jhb@freebsd.org>	 <b1fa29170802261507v5b336f36mcdab9bae65869e0a@mail.gmail.com> <b1fa29170802261519y7940b16em7c26e3175831ff14@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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?47C4A083.2050602>