summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorAmit Kumar Salecha2011-06-29 22:00:49 +0200
committerDavid S. Miller2011-07-01 07:32:49 +0200
commit0209bcd4d9ee66569d4ea76f9ab2de3a9c740c71 (patch)
tree7eca56aac7b37c5468a58616d896047d912f9bbf /tools
parentnet: ucc_geth: Omit check for multicast bit in netdev_for_each_mc_addr (diff)
downloadkernel-qcow2-linux-0209bcd4d9ee66569d4ea76f9ab2de3a9c740c71.tar.gz
kernel-qcow2-linux-0209bcd4d9ee66569d4ea76f9ab2de3a9c740c71.tar.xz
kernel-qcow2-linux-0209bcd4d9ee66569d4ea76f9ab2de3a9c740c71.zip
net: add external loopback test in ethtool self test
External loopback test can be performed by application without any driver support on normal Ethernet cards. But on CNA devices, where multiple functions share same physical port. Here internal loopback test and external loopback test can be initiated by multiple functions at same time. To co exist all functions, firmware need to regulate what test can be run by which function. So before performing external loopback test, command need to send to firmware, which will quiescent other functions. User may not want to run external loopback test always. As special cable need to be connected for this test. So adding explicit flag in ethtool self test, which will specify interface to perform external loopback test. ETH_TEST_FL_EXTERNAL_LB: Application set to request external loopback test ETH_TEST_FL_EXTERNAL_LB_DONE: Driver ack if test performed Signed-off-by: Amit Kumar Salecha <amit.salecha@qlogic.com> Reviewed-by: Ben Hutchings <bhutchings@solarflare.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions