|
Revision tags: v22.03, v22.03-rc4, v22.03-rc3, v22.03-rc2, v22.03-rc1 |
|
| #
7be78d02 |
| 29-Nov-2021 |
Josh Soref <[email protected]> |
fix spelling in comments and strings
The tool comes from https://github.com/jsoref
Signed-off-by: Josh Soref <[email protected]> Signed-off-by: Thomas Monjalon <[email protected]>
|
|
Revision tags: v21.11, v21.11-rc4, v21.11-rc3, v21.11-rc2, v21.11-rc1, v21.08, v21.08-rc4, v21.08-rc3, v21.08-rc2, v21.08-rc1, v21.05, v21.05-rc4, v21.05-rc3, v21.05-rc2, v21.05-rc1, v21.02, v21.02-rc4, v21.02-rc3, v21.02-rc2 |
|
| #
c0a8b024 |
| 25-Jan-2021 |
Heinrich Kuhn <[email protected]> |
net/nfp: read chip model from PluDevice register
For newer smartNIC NVRAM versions the chip model should be read from the PluDevice register as it provides the authoritative chip model/revision. Thi
net/nfp: read chip model from PluDevice register
For newer smartNIC NVRAM versions the chip model should be read from the PluDevice register as it provides the authoritative chip model/revision. This method of reading the chip model is backwards compatible with legacy NVRAM versions too.
Since the model number is purely used for reporting purposes, follow the hardware team convention of subtracting 0x10 from the PluDevice register to obtain the chip model/revision number.
Fixes: c7e9729da6b5 ("net/nfp: support CPP") Cc: [email protected]
Signed-off-by: Heinrich Kuhn <[email protected]> Signed-off-by: Simon Horman <[email protected]> Reviewed-by: Louis Peens <[email protected]>
show more ...
|
| #
df96fd0d |
| 29-Jan-2021 |
Bruce Richardson <[email protected]> |
ethdev: make driver-only headers private
The rte_ethdev_driver.h, rte_ethdev_vdev.h and rte_ethdev_pci.h files are for drivers only and should be a private to DPDK and not installed.
Signed-off-by:
ethdev: make driver-only headers private
The rte_ethdev_driver.h, rte_ethdev_vdev.h and rte_ethdev_pci.h files are for drivers only and should be a private to DPDK and not installed.
Signed-off-by: Bruce Richardson <[email protected]> Reviewed-by: Maxime Coquelin <[email protected]> Acked-by: Thomas Monjalon <[email protected]> Acked-by: Steven Webster <[email protected]>
show more ...
|
|
Revision tags: v21.02-rc1, v20.11, v20.11-rc5, v20.11-rc4, v20.11-rc3, v20.11-rc2, v20.11-rc1, v20.08, v20.08-rc4, v20.08-rc3, v20.08-rc2, v20.08-rc1, v20.05, v20.05-rc4, v20.05-rc3, v20.05-rc2, v20.05-rc1, v20.02, v20.02-rc4, v20.02-rc3, v20.02-rc2, v20.02-rc1, v19.11, v19.11-rc4, v19.11-rc3, v19.11-rc2, v19.11-rc1, v19.08, v19.08-rc4, v19.08-rc3, v19.08-rc2, v19.08-rc1, v19.05, v19.05-rc4, v19.05-rc3, v19.05-rc2 |
|
| #
0fec453d |
| 08-Apr-2019 |
Alejandro Lucero <[email protected]> |
net/nfp: check return value
Call to CPP read (nfp_cpp_readl()) can fail, return 0 on fail.
If the call to _nfp6000_cppat_mu_locality fails, the function needs to return with an error.
If the nfp_c
net/nfp: check return value
Call to CPP read (nfp_cpp_readl()) can fail, return 0 on fail.
If the call to _nfp6000_cppat_mu_locality fails, the function needs to return with an error.
If the nfp_cpp_readl() call fails just returns 0.
Coverity issue: 277209, 277215, 277225 Fixes: c7e9729da6b5 ("net/nfp: support CPP") Cc: [email protected]
Signed-off-by: Alejandro Lucero <[email protected]>
show more ...
|
|
Revision tags: v19.05-rc1, v19.02, v19.02-rc4, v19.02-rc3, v19.02-rc2, v19.02-rc1, v18.11, v18.11-rc5, v18.11-rc4, v18.11-rc3, v18.11-rc2, v18.11-rc1, v18.08, v18.08-rc3, v18.08-rc2, v18.08-rc1 |
|
| #
ebf2ed72 |
| 18-Jun-2018 |
Alejandro Lucero <[email protected]> |
net/nfp: use generic PCI config access functions
This patch avoids direct access to device config sysfs file using rte_pci_read_config instead.
Apart from replicating code, it turns out this direct
net/nfp: use generic PCI config access functions
This patch avoids direct access to device config sysfs file using rte_pci_read_config instead.
Apart from replicating code, it turns out this direct access does not always work if non-root users execute DPDK apps. In those cases it is mandatory to go through VFIO specific function for reading pci config space.
Signed-off-by: Alejandro Lucero <[email protected]>
show more ...
|
|
Revision tags: v18.05, v18.05-rc6 |
|
| #
5f6ed2f4 |
| 23-May-2018 |
Alejandro Lucero <[email protected]> |
net/nfp: fix lock file usage
DPDK apps can be executed as non-root users but current NFP lock file for avoiding concurrent accesses to CPP interface is precluding this option or requires to modify s
net/nfp: fix lock file usage
DPDK apps can be executed as non-root users but current NFP lock file for avoiding concurrent accesses to CPP interface is precluding this option or requires to modify system file permissions.
When the NFP device is bound to VFIO, this driver does not allow this concurrent access, so the lock file is not required at all.
OVS-DPDK as executed in RedHat distributions is the main NFP user needing this fix.
Fixes: c7e9729da6b5 ("net/nfp: support CPP")
Signed-off-by: Alejandro Lucero <[email protected]>
show more ...
|
|
Revision tags: v18.05-rc5, v18.05-rc4, v18.05-rc3, v18.05-rc2, v18.05-rc1 |
|
| #
c7e9729d |
| 05-Apr-2018 |
Alejandro Lucero <[email protected]> |
net/nfp: support CPP
CPP refers to the internal NFP Command Push Pull bus. This patch allows to create CPP commands from user space allowing to access any single part of the chip.
This CPP interfac
net/nfp: support CPP
CPP refers to the internal NFP Command Push Pull bus. This patch allows to create CPP commands from user space allowing to access any single part of the chip.
This CPP interface is the base for having other functionalities like mutexes when accessing specific chip components, chip resources management, firmware upload or using the NSP, an embedded arm processor which can perform tasks on demand.
NSP was the previous only way for doing things in the chip by the PMD, where a NSPU interface was used for commands like firmware upload or port link configuration. CPP interface supersedes NSPU, but it is still possible to use NSP through CPP.
CPP interface adds a great flexibility for doing things like extended stats or firmware debugging.
Signed-off-by: Alejandro Lucero <[email protected]>
show more ...
|