2021-10-08 06:53 (UTC-0700), William Tu: > This patch enables building the e1000 driver for Windows. > I tested using two Windows VM on top of VMware Fusion, > creating two e1000 devices with device ID 0x10D3, > verifying rx/tx works correctly using dpdk-testpmd.exe > rxonly and txonly mode. > > Signed-off-by: William Tu <u9012...@gmail.com> > Cc: Haiyue Wang <haiyue.w...@intel.com>
Will there be an accompanying kmods patch to add the device ID to .inf? With device ID added to netuio, in QEMU with -device e1000e, Tested-by: Dmitry Kozlyuk <dmitry.kozl...@gmail.com> > diff --git a/doc/guides/nics/e1000em.rst b/doc/guides/nics/e1000em.rst > index 041c9a09a3a5..03ae23838bfa 100644 > --- a/doc/guides/nics/e1000em.rst > +++ b/doc/guides/nics/e1000em.rst > @@ -1,6 +1,8 @@ > .. SPDX-License-Identifier: BSD-3-Clause > Copyright(c) 2010-2014 Intel Corporation. > > +.. include:: <isonum.txt> > + > Driver for VM Emulated Devices > ============================== > > @@ -153,3 +155,14 @@ The following are known limitations: > #. Qemu e1000 only supports one interrupt source, so link and Rx interrupt > should be exclusive. > > #. Qemu e1000 does not support interrupt auto-clear, application should > disable interrupt immediately when woken up. > + > +Windows Configuration > +--------------------- > + > +- Follow the :doc:`guide for Windows <../windows_gsg/run_apps>` > + to setup the basic DPDK environment. > + > +- Identify the Intel\ |reg| Ethernet adapter. > + > +- To load NetUIO driver, follow the steps mentioned in `dpdk-kmods repository > + <https://git.dpdk.org/dpdk-kmods/tree/windows/netuio/README.rst>`_. There is nothing special about setting up this device on Windows. I think we don't need this part.
