sowmini.varadhan at sun.com wrote:
> On (07/18/07 13:41), Garrett D'Amore wrote:
>
>> Simple recommendation:
>>
>> * Allow for tristate values:
>>
>> cap_pause = both, tx, rx
>> adv_pause = both, tx, rx
>> lp_pause = both, tx, rx
>> link_pause = both, tx, rx
>>
>>
>
> Of these, only the adv_pause values can be set, right? (i.e., the others
> are read-only values, I think).
>
>
>> That would be far, far simpler.
>>
>
> agreed. But then the question arises, what to do about existing definitions
> from ieee802.3(5)? Should we leave that as "legacy ndd" support, and
> add new documentation for the improved definitions?
>
Actually this is one of those cases where I think the existing interface
is so busted that nobody will complain too loudly if we just abandon the
old interfaces. I will argue the case this way if it is so presented at
PSARC.
-- Garrett
>
>> These tables have to be extended to add 1g and 10g support, btw.
>>
>>
>>> ------------------------------------------------------
>>> capable advertised link-partner
>>> advertised
>>> ------------------------------------------------------
>>> autoneg
>>> speed
>>> duplex
>>> rem_fault
>>> pause
>>> asm_pause
>>> ------------------------------------------------------
>>>
>
> Any specific suggestions in addition to those covered in the
> discussion at
> http://mail.opensolaris.org/pipermail/brussels-dev/2007-June/000256.html
> ??
>
> --Sowmini
>
