lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 01 Jun 2007 15:59:29 -0700 (PDT) From: David Miller <davem@...emloft.net> To: jharan@...cade.COM Cc: jeff@...zik.org, linux-net@...r.kernel.org, netdev@...r.kernel.org Subject: Re: ETHTOOL_GSET IOCTL on GigE links From: "Jeff Haran" <jharan@...cade.COM> Date: Fri, 1 Jun 2007 15:51:18 -0700 > OK, but my question remains. In the case where a device supports one set > of speeds via autonegotiation and another set via forcing, how does one > tell which speeds can be forced and which can be autonegotiated? Unfortunately, as you have noted, this information is not given at the moment. I got bit by this the other week when I wanted to try forcing gigabit on a tg3 and the driver wouldn't allow it because it only allows forcing link speeds at 10/100 on copper links. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists