<div>That's clear now! Thank you, Joshua!</div><div><br></div><br><div class="gmail_quote">On Thu, Jun 17, 2010 at 11:55 PM, Joshua Oreman <span dir="ltr"><<a href="mailto:oremanj@rwcr.net">oremanj@rwcr.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">[Please keep the list in the Cc]<br>
<div class="im"><br>
On Thu, Jun 17, 2010 at 5:37 AM, Sean Shoufu Luo <<a href="mailto:luoshoufu@gmail.com">luoshoufu@gmail.com</a>> wrote:<br>
> Hi Josh,<br>
> Thank you for informative explain on UNDI. I still have a question.<br>
> According to what you said, my understand is UNDI build (undi.zrom) contains<br>
> DHCP/TFTP/... and UNDI driver, and it must work with vendor ROM that exposes<br>
> an UNDI. My question is who provides the UNDI ROM which is loaded to be<br>
> below 1M memory, undi.zrom or vendor ROM?<br>
<br>
</div>So, there are two components here:<br>
<br>
- The UNDI interface<br>
- The UNDI driver<br>
<br>
(Sadly, as far as I know these don't have a consistent naming.) The<br>
UNDI interface is provided by an existing vendor PXE ROM or<br>
specific-driver Etherboot or gPXE ROM (e.g. rtl8139.zrom). It has a<br>
special header so it can be found and loaded in such a way that it<br>
will just expose the UNDI API. The UNDI driver (in undi.zrom and<br>
friends) looks for a ROM that implements the UNDI interface, loads it,<br>
and sends and receives DHCP/TFTP/etc packets using the UNDI API that<br>
it finds. As I said before, *undi.zrom does not make sense and will<br>
never work*; the UNDI driver should be part of a PXE or CDROM or<br>
[etc.] build of Etherboot/gPXE with a *different*, driver-specific ROM<br>
already present in the system.<br>
<br>
The main use of UNDI is to allow booting on systems that<br>
Etherboot/gPXE does not have native driver support for. For it to<br>
work, you need to still have the vendor PXE ROM in the system.<br>
<br>
-- Josh<br>
<div><div></div><div class="h5"><br>
> Thanks again<br>
> -Sean-<br>
> On Thu, Jun 17, 2010 at 10:59 AM, <<a href="mailto:oremanj@gmail.com">oremanj@gmail.com</a>> wrote:<br>
>><br>
>> Hi Sean,<br>
>><br>
>> A few things:<br>
>><br>
>> Etherboot is out of date and in maintenance mode only. Please use gPXE if<br>
>> you can, as it has many more features and fewer bugs. :-) If there's a<br>
>> specific reason you need to use Etherboot over gPXE, let us know; we'd like<br>
>> to fix it.<br>
>><br>
>> UNDI builds of Etherboot and gPXE are meant to be used in tandem with a<br>
>> preexisting vendor ROM that exposes an UNDI interface. Thus, the combination<br>
>> UNDI + ROM in the same build makes no sense. Etherboot and gPXE expose an<br>
>> UNDI interface no matter what, and in this case Etherboot finds and attempts<br>
>> to load *itself* as the underlying "real" vendor ROM. The results are<br>
>> predictably awful.<br>
>><br>
>> So what you really want is a ROM with a specific driver included (not<br>
>> UNDI). Also, consider using gPXE instead of Etherboot.<br>
>><br>
>> Happy hacking :-)<br>
>><br>
>> -- Josh<br>
>> Sent via BlackBerry by AT&T<br>
>><br>
>> -----Original Message-----<br>
>> From: Sean Shoufu Luo <<a href="mailto:luoshoufu@gmail.com">luoshoufu@gmail.com</a>><br>
>> Date: Thu, 17 Jun 2010 10:48:36<br>
>> To: <<a href="mailto:gpxe-devel@etherboot.org">gpxe-devel@etherboot.org</a>><br>
>> Subject: [gPXE-devel] what is undi.zrom in gPXE?<br>
>><br>
>> _______________________________________________<br>
>> gPXE-devel mailing list<br>
>> <a href="mailto:gPXE-devel@etherboot.org">gPXE-devel@etherboot.org</a><br>
>> <a href="http://etherboot.org/mailman/listinfo/gpxe-devel" target="_blank">http://etherboot.org/mailman/listinfo/gpxe-devel</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> Face to sun<br>
><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Face to sun<br>