1*5a2cc190SJeff Kirsher# 2*5a2cc190SJeff Kirsher# Mellanox driver configuration 3*5a2cc190SJeff Kirsher# 4*5a2cc190SJeff Kirsher 5*5a2cc190SJeff Kirsherconfig MLX4_EN 6*5a2cc190SJeff Kirsher tristate "Mellanox Technologies 10Gbit Ethernet support" 7*5a2cc190SJeff Kirsher depends on PCI && INET 8*5a2cc190SJeff Kirsher select MLX4_CORE 9*5a2cc190SJeff Kirsher select INET_LRO 10*5a2cc190SJeff Kirsher ---help--- 11*5a2cc190SJeff Kirsher This driver supports Mellanox Technologies ConnectX Ethernet 12*5a2cc190SJeff Kirsher devices. 13*5a2cc190SJeff Kirsher 14*5a2cc190SJeff Kirsherconfig MLX4_CORE 15*5a2cc190SJeff Kirsher tristate 16*5a2cc190SJeff Kirsher depends on PCI 17*5a2cc190SJeff Kirsher default n 18*5a2cc190SJeff Kirsher 19*5a2cc190SJeff Kirsherconfig MLX4_DEBUG 20*5a2cc190SJeff Kirsher bool "Verbose debugging output" if (MLX4_CORE && EXPERT) 21*5a2cc190SJeff Kirsher depends on MLX4_CORE 22*5a2cc190SJeff Kirsher default y 23*5a2cc190SJeff Kirsher ---help--- 24*5a2cc190SJeff Kirsher This option causes debugging code to be compiled into the 25*5a2cc190SJeff Kirsher mlx4_core driver. The output can be turned on via the 26*5a2cc190SJeff Kirsher debug_level module parameter (which can also be set after 27*5a2cc190SJeff Kirsher the driver is loaded through sysfs). 28