Re: Etherboot and gpxe

On Thu, 2009-08-06 at 15:45 -0700, Joyce Yu wrote:
> 
> Here is the output of the size. They looked similar:
> In etherboot;
>    text    data     bss     dec     hex filename
>   20937      48   96624  117609   1cb69 xxxx.o
> 
> In gPXE:
>    text    data     bss     dec     hex filename
>   21461      40   96624  118125   1cd6d xxxx.o

The gPXE driver size is only a tiny bit more (500 bytes). That's a
*mighty* large driver, though. There are only two in the gPXE tree that
are larger in .text (tg3 and e1000). For comparison, rtl8139 is 3097
bytes. It's going to be pretty difficult to make a 32kb ROM, even
compressed, when your driver is 20kb.

I suspect the difference in .o file sizes comes from the fact that gPXE
compiles with debugging symbols by default. This does not increase the
size of the ROM.

> What can I do for the config/defaults.h?

Ack, oops; I meant config/general.h, sorry. It contains several #defines
controlling whether gPXE will be compiled with various features.

> If the ROM images has to be more than 32k, it become useless in all my
> systems. There are other I/O cards share 128k Option ROM space in
> these systems.

Are you restricted to exactly 32kb, or can you go a bit over? ROM images
don't have to be a "nice" size.

-- Josh

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

_______________________________________________
Etherboot-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBKe2DyI6LPMrSI3tYRAl0MAJ9Wvdi+9CPUlKbaZNyeLzHtT/dnuACaA24y
iAGZ+QBQvDfOT2SVgn8t/40=
=4kzM
-----END PGP SIGNATURE-----