[EMAIL PROTECTED] writes:
> On (06/19/07 07:51), James Carlson wrote:
> > [EMAIL PROTECTED] writes:
> > > Let me ask the question another way: by setting speed and duplex
> > > separately,
> > > is it actually possible to hit a permutation that would not happen
> > > with the predefined <speed>{f,h}dx definition?
> >
> > Yes. Half-duplex above 100Mbps gets pretty strange, and I suspect
> > many (perhaps most) adapters don't support it. See 802.3-2002 section
> > 4.1.2.1.1, 4.2.3.4, and 4.2.9. It's definitely a case of "so, remind
> > me, just what problem was it you were solving .... ?"
>
> Interesting.
>
> I'll update the doc in the next rev to remove the "link_speed" and
> "link_duplex" refs from the Appendix, and to use the existing
> adv_*_cap definitiosn from ieee802.3(5). However, the ieee802.3(5)
> man page itself documents usage of 100/hdx and 1000/hdx permutations,
> so the above strange usage would still be present (where supported by
> the underlying driver).
I think "where supported" is the key bit here.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]