UNDI ROM code etc. when you just want a "undi.kpxe"-type image).

This driver cannot be used in conjunction with any other driver (it will
crash), or in any other format than .kpxe (it just won't find any network
devices).

it directly to undi_load_pci().

addresses if the signature checks fail.

we can never return to the PXE stack and must always use INT 18.

loader.

UNDI stack.

Record all information required for populating a struct undi_device.

Make debugging output more human-readable.

able to populate the structure.

and call UNDI_SHUTDOWN first to make sure the NIC is in a safe state.

memory (unless we get an error while stopping the base code).  Leave UNDI
resident (though stopped) for .kpxe.

Still need to add code to record the device identification parameters
prior to stopping UNDI.

undi_rom rather than struct pxe_driver.  (This is part of the naming
consistency fixes).

function prefix "undinet_" and the variable name "undinic" in undinet.c,
so that we can reserve the variable name "undi" for a struct undi_device.

The idea is that we preserve the Etherboot 5.4 convention that the "UNDI"
code refers to our using an underlying UNDI stack, while the "PXE" code
refers to our providing a PXE API.

way everything remains consistent if the probe() ends up creating child
devices.

UNDI_GET_INFORMATION calls into drivers/net/undi.c.  undi_probe() now
gets given a pxe_device representing a PXE stack that has been loaded
into memory but not initialised in any way.

Handle failures in undi_open() properly.

and matching them up to (e.g. PCI) devices.

functionality is now in pxebus.c.  (Not all bus functionality is ported
across yet.)

lying about in memory, not for loading from ROM), and UNDI net driver.