<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi. I have a question about the 5719 / 5720 TX DMA workaround fix that was committed to the tg3 driver in the Linux kernel. The iPXE's tg3 driver variant for 5719 / 5270 does not contain this. I have a system where I do see the TX DMA stall when Linux loads the regular tg3 driver, but haven’t been able to reproduce it when running iPXE on the same device. I’m trying to ascertain why iPXE will not fail with the same error - is there a fundamental difference in how iPXE uses TX DMA compared to the mainstream tg3 driver?</div><div><br></div><div>Thanks - Atif</div><div><br></div><div><a href="http://kernel.opensuse.org/cgit/kernel/commit/?id=091f0ea30074bc43f9250961b3247af713024bc6">http://kernel.opensuse.org/cgit/kernel/commit/?id=091f0ea30074bc43f9250961b3247af713024bc6</a></div><div><blockquote type="cite"> After Power-on-reset, the 5719's TX DMA length registers may contain<br>uninitialized values and cause TX DMA to stall. Check for invalid<br>values and set a register bit to flush the TX channels. The bit<br>needs to be turned off after the DMA channels have been flushed</blockquote></div></body></html>