On 10/3/2017 12:51 PM, Tomasz Duszynski wrote: > Add documentation for the MRVL NET PMD driver. > > Signed-off-by: Jacek Siuda <j...@semihalf.com> > Signed-off-by: Tomasz Duszynski <j...@semihalf.com>
<...> > +; > +[Features] > +Speed capabilities = Y This doesn't seems correct please check doc/guides/nics/features.rst > +Link status = Y > +MTU update = Y > +Jumbo frame = Y > +Promiscuous mode = Y > +Allmulticast mode = Y > +Unicast MAC filter = Y > +Multicast MAC filter = Y > +RSS hash = Y > +VLAN filter = Y > +CRC offload = Y > +L3 checksum offload = Y > +L4 checksum offload = Y > +Packet type parsing = Y > +Basic stats = Y > +Stats per queue = Y > +ARMv8 = Y Is other architecture not supported or not tested? > +Usage doc = Y <...> > +Prerequisites > +------------- > + > +- MUSDK (Marvell User-Space SDK) sources available > + `here > <https://github.com/MarvellEmbeddedProcessors/musdk-marvell/tree/musdk-armada-17.08>`_. Is this 17.08 by change related to DPDK version, I mean is there any relation between DPDK version and musdk library version? > + > + MUSDK is a light-weight library that provides direct access to Marvell's > + PPv2 (Packet Processor v2). Alternatively prebuilt MUSDK library can be > + requested from `Marvell Extranet <https://extranet.marvell.com>`_. Once > + approval has been granted, library can be found by typing ``musdk`` in > + search box. What is the condition of having an approval? > + > +- DPDK environment > + > + Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to > setup > + DPDK environment. > + > + <...> > +Building DPDK > +------------- > + > +Driver needs precompiled MUSDK library during compilation. Detailed build > +process is described in library's documentation under ``doc`` directory. > + > +Before the DPDK build process the environmental variable ``LIBMUSDK_PATH`` > with > +the path to the MUSDK installation directory needs to be exported. > + > +Usage Example > +------------- > + > +MRVL PMD requires extra kernel modules to function properly: > + > +.. code-block:: console > + > + insmod musdk_uio.ko > + insmod mv_pp_uio.ko > + insmod mvpp2x_sysfs.ko Why these kernel modules are required and how one can obtain them? These are out of tree kernel modules right? <...>