I have successfully booted DOS via iSCSI and PXELINUX via TFTP with this
version of the e1000 driver.

implemented smbios_get_uuid().

potentially exorbitant amounts of stack space.

There may still be an issue with memory handling, since it seems to
die ungracefully when ARP packets come in after loading a kernel.
Something to debug.

autonegotiation still needs work.  receive is not working yet.

needing to know the gPXE internal ROM name.

It is likely we will rename e1000_main to e1000 when the new e1000 driver is debugged.

We didn't specify values for MaxRecvDataSegmentLength and
MaxBurstLength (to save space, since we were happy with the
RFC-defined default values of 8kB and 256kB respectively).  However,
the OpenSolaris target (incorrectly) assumes default values of zero
for these parameters.

The upshot was that the OpenSolaris target would get stuck in an
endless loop trying to send us the first 512-byte sector, zero bytes
at a time, and would eventually run out of memory and core-dump.

Fixed by explicitly specifying the default values for these two
parameters.

allowing any space for this, which makes it surprising that bzImage
loading ever worked.

memory map.  (We achieve this by setting CF on the last entry if it is
zero-length; this avoids the need to look ahead to see at each entry
if the *next* entry would be both the last entry and zero-length).

This fixes the "0kB base memory" error message upon starting Windows
2003 on a SunFire X2100.

memory map.  (We achieve this by setting CF on the last entry if it is
zero-length; this avoids the need to look ahead to see at each entry
if the *next* entry would be both the last entry and zero-length).

This fixes the "0kB base memory" error message upon starting Windows
2003 on a SunFire X2100.

packet, to work around the problem whereby small TX rings get backed
up because we haven't yet poll()ed for TX completions.

packet, to work around the problem whereby small TX rings get backed
up because we haven't yet poll()ed for TX completions.

byte, rather than the number of permissible bytes (i.e. subtract one
from the value under the previous definition to get the value under
the new definition).

This avoids integer overflow on 64-bit kernels, where
bzhdr.initrd_addr_max may be 0xffffffffffffffff; under the old
behaviour we set mem_limit equal to initrd_addr_max+1, which meant it
ended up as zero.  Kernel loads would fail with ENOBUFS.

any rewrite.

DBG_PRINTF() and assert().

confusing to read the code.

stack; it breaks vmxassist.

outside of librm.S.

work around limitations in real-mode virtualisation support on Intel
VT-capable chips.

Added redundant call to get_memmap() in int13_boot() immediately
before jumping to boot sector, to assist in debugging.

Added redundant call to get_memmap() in int13_boot() immediately
before jumping to boot sector, to assist in debugging.