Garrett D'Amore wrote: > Steven Stallion wrote: >> All, >> >> Quick question about the various adv_ and en_ properties supported by >> dladm: >> >> >From what I understand, the adv_ properties are to be set by the driver >> (i.e. read-only) for the configurations it supports. >> >> What purpose do the en_ properties serve? Are these properties a way of >> allowing the user to specify a subset of configurations a driver may use >> to select the best configuration available? >> >> Why would this be desired over setting the duplex and speed properties >> instead? >> > > en_xxx set the bits used in 802.3u (MII) configuration. Directly > setting the duplex and speed properties would be a subset of > functionality. (Because using the en_xxx bits, you can offer to support > more than a single configuration ... e.g. you could offer to support 100 > FDX *and* 10 FDX.)
Okay, so lets say that en_10fdx_cap and en_100hdx_cap are set; does this affect negotiation? Is there a heuristic for choosing the correct cap? _______________________________________________ networking-discuss mailing list [email protected]
