f4b6bcc700
Being able to build devlink as a module causes growing pains. First all drivers had to add a meta dependency to make sure they are not built in when devlink is built as a module. Now we are struggling to invoke ethtool compat code reliably. Make devlink code built-in, users can still not build it at all but the dynamically loadable module option is removed. Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com> Acked-by: Jiri Pirko <jiri@mellanox.com> Signed-off-by: David S. Miller <davem@davemloft.net>
48 lines
1.2 KiB
Plaintext
48 lines
1.2 KiB
Plaintext
#
|
|
# Mellanox driver configuration
|
|
#
|
|
|
|
config MLX4_EN
|
|
tristate "Mellanox Technologies 1/10/40Gbit Ethernet support"
|
|
depends on PCI && NETDEVICES && ETHERNET && INET
|
|
select MLX4_CORE
|
|
imply PTP_1588_CLOCK
|
|
---help---
|
|
This driver supports Mellanox Technologies ConnectX Ethernet
|
|
devices.
|
|
|
|
config MLX4_EN_DCB
|
|
bool "Data Center Bridging (DCB) Support"
|
|
default y
|
|
depends on MLX4_EN && DCB
|
|
---help---
|
|
Say Y here if you want to use Data Center Bridging (DCB) in the
|
|
driver.
|
|
If set to N, will not be able to configure QoS and ratelimit attributes.
|
|
This flag is depended on the kernel's DCB support.
|
|
|
|
If unsure, set to Y
|
|
|
|
config MLX4_CORE
|
|
tristate
|
|
depends on PCI
|
|
default n
|
|
|
|
config MLX4_DEBUG
|
|
bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
|
|
depends on MLX4_CORE
|
|
default y
|
|
---help---
|
|
This option causes debugging code to be compiled into the
|
|
mlx4_core driver. The output can be turned on via the
|
|
debug_level module parameter (which can also be set after
|
|
the driver is loaded through sysfs).
|
|
|
|
config MLX4_CORE_GEN2
|
|
bool "Support for old gen2 Mellanox PCI IDs" if (MLX4_CORE)
|
|
depends on MLX4_CORE
|
|
default y
|
|
---help---
|
|
Say Y here if you want to use old gen2 Mellanox devices in the
|
|
driver.
|