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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 01 Jun 2007 18:40:04 -0400
From:	Jeff Garzik <>
To:	Jeff Haran <jharan@...cade.COM>
CC:, netdev <>
Subject: Re: ETHTOOL_GSET IOCTL on GigE links

Jeff Haran wrote:
> With 10/100 Mbps links it wasn't such an issue since the devices tend to
> support the same forced speeds and duplexities as they are capable of
> negotiating, but with GigE links that's not always the case, at least
> not according to what I've read. For instance, the following doc from
> Sun says that IEEE
> 802.3ab says you can't force 1000Base-T over copper media (see page 4),
> whereas some other physical media allow GigE to run without
> autonegotiation (there's apparently this "serdes" interface that allows
> it, for instance).
> Seems like there should be another field named something like
> supported_forced to indicate what can be forced on the interface. Either
> that or some more SUPPORTED_* bits to indicate supported forced modes.

The 'supported' field has nothing at all to do with auto-negotiation.

The driver should list all possibilities in that field, even if some are 
ONLY supported via 'forced' selection.


P.S. is a far more active list, and is where 
the network stack/driver developers appear.
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists