setup.S.

highmem data, so decompress16 will be able to unpack blocks bigger
than 64kB.

running the decompresser in 16:16 protected mode using the real-mode
stack.  However, there's an even simpler way to do it...

closed() method with a reason code.

connection and so legitimately ignores acked() and senddata().

compile, even if it won't yet be safe.

take ownership of the packet, rather than doing so only if they return
success.  This breaks semantic compatibility with Linux's
hard_start_xmit() method, but means that we don't have to worry so much
about error cases.

Split mechanism of processing received packets (net_rx_process()) out
from policy (net_step()), preparatory to putting net_step() in a separate
object.

Yes, you really can do it in 65 bytes.

Create something that might be usable as a symbol list for bochs'
internal debugger.

of them in one go.

EBADIMG has been replaced by ENOEXEC, and EIMGRET by ECANCELED.

checked-out copy.

crossings.

alignment and size are both powers of two, and there's no way to
specify an alignment through the malloc() interface anyway.

aligned blocks.

Moved header to include/malloc.h, since we now also provide the
POSIX-like malloc()/free() pair.

Not yet tested.

power-of-two up from a given constant via
  ( 1 << fls ( constant - 1 ) )

fls(), flsl(), ffs() and ffsl() appear in strings.h according to
POSIX.

Tie into existing driver API; we'll fix that up soon.

even when __atribute__ (( unused )) is correctly set...

Doing so, in fact, seems to expose an assembler bug; (a-b-0) is
apparently not the same as (a-b).  Go figure.

I want to get to the point where any header in include/ reflects a
standard user-level header (e.g. a POSIX header), while everything that's
specific to gPXE lives in include/gpxe/.  Headers that reflect a Linux
header (e.g. if_ether.h) should also be in include/gpxe/, with the same
name as the Linux header and, preferably, the same names used for the
definitions.

implementation allows for only one, and does so without compromising on
the efficiency of static allocation).

Link-layer protocols are cleanly separated from the device drivers.

Network-layer protocols are cleanly separated from individual network
devices.

Link-layer and network-layer protocols are cleanly separated from each
other.