[gPXE] Legacy UNDI PXE driver and GPXE integration.
Shao Miller
Shao.Miller at yrdsb.edu.on.ca
Thu Jan 7 19:21:38 EST 2010
Sivakumar Subramani wrote:
>
> ... ... ...
> We have vendor-specific UNDI ROM driver for our x3100 10GbE NIC, that
> works well with undionly.kpxe.
>
If you mean your ROM -> undionly.kpxe works, that's good.
> However we would like to develop complete gPXE ROM and put it on the
> card, rather than use chainloading with undionly.kpxe.
>
Perhaps you could embed undionly.kpxe into your ROM and chain it
automatically.
> We understand
> that conventional way of doing that is via a NIC driver similar to the
> ones in gpxe\src\drivers\net,
>
That's what a lot of folks do, which contributes to gPXE's driver set
for the benefit of its users.
> but since we already have working UNDI
> driver that works with undioly.kpxe (as well as with other proprietary
> PXE code), we wonder if it is possible to compile it with gpxe files to
> produce a complete PXE ROM?
> ... ... ...
>
Embedding some proprietary ROM into a gPXE ROM seems a little inside-out
to me. Anything's possible... gPXE would have to find your UNDI/PXE
stacks, so you'd have to hack gPXE to look for them in your UNDI ROM
image that you embed, plus you'd have to modify gPXE to otherwise
completely ignore your UNDI ROM embedded image so that it is not used as
a boot file or initrd.
Perhaps you'd like to tackle porting the driver to gPXE by studying some
gPXE drivers? You need not worry about the UNDI portions of your code,
since gPXE takes care of all of that. Just the hardware-specific
portions will need porting. It might make for a unique challenge for you.
Good luck!
- Shao Miller
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://etherboot.org/pipermail/gpxe/attachments/20100107/2edb2770/attachment.html
More information about the gPXE
mailing list