2017-03-24 14:30, Bruce Richardson:
> When loading nic_uio from /boot/loader.conf as specified in the Getting
> Started Guide doc, the NIC devices were not bound at boot. Unloading the
> nic_uio driver and reloading it would cause them to be bound, however.
>
> The root cause appears to be the fact that when the module is loaded at
> boot, the call to find the pci device when parsing the b:d:f parameter
> fails to return the device. That means that later on when the device
> is probed as part of a PCI scan, no action is taken as it's not recorded
> as a device to be used.
>
> We fix this by having the b:d:f string parsed again on probe if the
> initial check to see if it's an already-known device fails. In my tests,
> this causes the NIC devices to be successfully bound at boot time, as
> well as leaving things working as before in the case the module is loaded
> post-boot.
>
> Fixes: 764bf26873b9 ("add FreeBSD support")
>
> Signed-off-by: Bruce Richardson <bruce.richard...@intel.com>
Cc: sta...@dpdk.org
Applied, thanks
