Hello,
On Sat, Jun 8, 2024 at 1:32 AM Nandini Rangaswamy
<nandini.rangasw...@broadcom.com> wrote:
> Thanks for your email. I inspected meson build output and do see that netvsc
> is in the list of enabled drivers.
> ===============
> Drivers Enabled
> ===============
>
> common:
> iavf, mlx5, qat,
> bus:
> auxiliary, pci, vdev, vmbus,
> mempool:
> bucket, ring, stack,
> dma:
>
> net:
> af_packet, bond, e1000, ena, failsafe, gve, i40e, iavf,
> ice, igc, ixgbe, kni, mlx5, netvsc, ring, tap,
> vdev_netvsc, vhost, virtio, vmxnet3,
Ok, so the driver seems indeed part of this build, yet it was not
functional at runtime?
Could you confirm this driver was indeed embeeded in (*statically*
linked) testpmd?
$ ./usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd | grep -i vsc
"name": "net_netvsc",
"name": "net_vdev_netvsc",
>
> Also, i changed the meson.build default_library=shared from static and it
> worked.
Mm, the fact that changing link mode fixes the issue points at a link issue.
There is a bug with old pkg-config tool (<= 0.27 iirc) that does not
process correctly dpdk .pc (for static link).
It is worth checking which version of pkgconf is used in openwrt.
--
David Marchand
