From: Michael Brown Date: Tue, 3 Jul 2007 13:43:57 +0000 (+0100) Subject: It's not just Etherboot that fails to generate TX completions. X-Git-Url: http://git.etherboot.org/people/sha0/gpxe.git/commitdiff_plain/0958726ebb55b9d09d257f0af5c9297a00bb14a7 It's not just Etherboot that fails to generate TX completions. --- diff --git a/src/arch/i386/drivers/net/undinet.c b/src/arch/i386/drivers/net/undinet.c index 07106591..dc4ef98f 100644 --- a/src/arch/i386/drivers/net/undinet.c +++ b/src/arch/i386/drivers/net/undinet.c @@ -335,8 +335,8 @@ static int undinet_transmit ( struct net_device *netdev, /* Technically, we ought to make sure that the previous * transmission has completed before we re-use the buffer. - * However, this would break a gPXE-running-over-Etherboot - * setup, since Etherboot fails to generate TX completions. + * However, many PXE stacks (including at least some Intel PXE + * stacks and Etherboot 5.4) fail to generate TX completions. * In practice this won't be a problem, since our TX datapath * has a very low packet volume and we can get away with * assuming that a TX will be complete by the time we want to