I'm also curious about these comments in the iPXE source code if anybody
has any insight. (The NIC comes up and establishes link very quickly in
iPXE.)
/** The i219 has a seriously broken reset mechanism */
#define INTEL_I219 ( INTEL_NO_PHY_RST | INTEL_RST_HANG )
from:
https://git.ipxe.org/ipxe.git/blob/master:/src/drivers/net/intel.h#l319
And to ease the code-spelunking, the code that handles INTEL_NO_PHY_RST
is at:
https://git.ipxe.org/ipxe.git/blob/master:/src/drivers/net/intel.c#l305
and INTEL_RST_HANG is at:
https://git.ipxe.org/ipxe.git/blob/master:/src/drivers/net/intel.c#l643
and mentions an "undocumented bit in FEXTNVM11 to work around an errata
in i219 devices that will otherwise cause a complete datapath hang at
the next device reset".
Thanks again for any insight, especially if there are similar things in
the e1000e kernel driver for the I219.
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel Ethernet, visit
https://forums.intel.com/s/topic/0TO0P00000018NbWAI/intel-ethernet
