RE: [802.3ae] Clause 49 loopback
Brian,
49.2.14.4 specifies the behavior of clause 49 while in loopback mode and it
makes mandatory statements so it is consistant with the behavior that was
agreed to.
Regards,
Pat
-----Original Message-----
From: THALER,PAT (A-Roseville,ex1)
Sent: Friday, August 31, 2001 10:49 AM
To: 'brian.cruikshank@xxxxxxxxxxxxx'; THALER,PAT (A-Roseville,ex1)
Cc: stds-802-3-hssg@xxxxxxxx
Subject: RE: [802.3ae] Clause 49 loopback
The following is what we agreed to in July:
Loopback
X PCS none
X PMA mandatory
R PCS mandatory
R PMA optional
The PCS/PMA for each type has one mandatory loopback but the location is
different for X and R.
Pat
-----Original Message-----
From: brian.cruikshank@xxxxxxxxxxxxx
[mailto:brian.cruikshank@xxxxxxxxxxxxx]
Sent: Friday, August 31, 2001 8:36 AM
To: pat_thaler@xxxxxxxxxxx
Cc: stds-802-3-hssg@xxxxxxxx
Subject: [802.3ae] Clause 49 loopback
Pat,
I have a quick question for you.
I just noticed that some loopbacks have now become optional.
It is now optional for one XGXS and PMAs.
Clause 45 indicates a bit for Clause 49 loopback (it is not in a special
option location such as the Phy XGXS).
Clause 49 refers to loopback, but in conjunction with the optional PMA
loopback.
Clause 49 refers to loopback later but in conjuction with the setting of a
bit in Clause 45.
From this information, it looks like it might be mandatory, but there is
not a PICS in Clause 49 for it.
Is loopback on 64b66b supposed to be optional or mandatory?
____________________________________________________
Brian Cruikshank
Mindspeed Techologies
Conexant Systems
5555 Central Ave
Boulder, CO 80301
Phone: (303) 543-2023
Cell: (303) 641-9528
Fax: (303) 543-2099
Email: brian.cruikshank@xxxxxxxxxxxxx