IEEE
`Std 802.3u-1995
`
`28.2.3.4.11 Use of Next Pages
`
`SUPPLEMENT TO 802.3:
`
`Both devices must indicate Next Page ability for either to commence exchange of Next Pages.
`a)
`If both devices are Next Page able, then both devices shall send at least one Next Page.
`b)
`c) Next Page exchange shall continue until neither device on a link has more pages to transmit as indi-
`cated by the NP bit. A Message Page with a Null Message Code Field value shall be sent if the
`device has no other information to transmit.
`
`e)
`
`d) A Message Code can carry either a specific message or information that defines how following
`Unformatted Page(s) should be interpreted.
`If a Message Code references Unformatted Pages, the Unformatted Pages shall immediately follow
`the referencing Message Code in the order specified by the Message Code.
`Unformatted Page users are responsible for controlling the format and sequencing for their Unfor-
`matted Pages.
`
`i)
`
`28.2.3.4.12 MII register requirements
`
`The Next Page Transmit register defined in 28.2.4.1.6 shall hold the Next Page to be sent by Auto-Negotia-
`tion. Received Next Pages may be stored in the Auto-Negotiation link partner ability register.
`
`28.2.3.5 Remote fault sensing function
`
`The Remote Fault function may indicate to the Link Partner that a fault condition has occurred using the
`Remote Fault bit and, optionally, the Next Page function.
`
`Sensing of faults in a device as well as subsequent association of faults with the Remote Fault bit shall be
`optional. If the Local Device has no mechanism to detect a fault or associate a fault condition with the
`received Remote Fault bit indication, then it shall transmit the Remote Fault bit with the value contained in
`the Auto-Negotiation advertisement register bit (4.13).
`
`A Local Device may indicate it has sensed a fault to its Link Partner by setting the Remote Fault bit in the
`Auto-Negotiation advertisement register and renegotiating.
`
`If the Local Device sets the Remote Fault bit to logic one, it may also use the Next Page function to specify
`information about the fault that has occurred. Remote Fault Message Page Codes have been specified for this
`purpose.
`
`The Remote Fault bit shall remain set until afier successfirl negotiation with the base Link Code Word, at
`which time the Remote Fault bit shall be reset to a logic zero. On receipt of a base Link Code Word with the
`Remote Fault bit set to logic one, the device shall set the Remote Fault bit in the MII status register (1.4) to
`logic one if the MII management function is present.
`
`28.2.4 Management function requirements
`
`The management interface is used to communicate Auto-Negotiation information to the management entity.
`If an M11 is physically implemented, then management access is via the MII Management interface. Where
`no physical embodiment of the M11 exists, an equivalent to MH registers 0, 1, 4, 5, 6, and 7 (clause 22) are
`recommended to be provided.
`
`28.2.4.1 Media Independent Interface
`
`The Auto-Negotiation function shall have five dedicated registers:
`
`a) MII control register (register 0).
`b)
`lVHI status register (register 1).
`
`This is ar124>g'chive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`bit 1025
`
`
`
`Aerohive - Exhibit 1025
`0269
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`c) Auto-Negotiation advertisement register (register 4).
`cl) Auto-Negotiation link partner ability register (register 5).
`e) Auto-Negotiation expansion register (register 6).
`
`If the Next Page fimction is implemented, the Auto-Negotiation Next Page Transmit Register (register 7)
`shall be implemented.
`
`28.2.4.1.1 Mll control register
`
`MII control register (register 0) provides the mechanism to disable/enable and/or restart Auto—Negotiation.
`The definition for this register is provided in 22.2.4.1.
`
`The Auto—Negotiation fimction shall be enabled by setting bit 0.12 to a logic one. If bit 0.12 is set to a logic
`one, then bits 0.13 and 0.8 shall have no effect on the link configuration, and the Auto-Negotiation process
`will determine the link configuration. If bit 0.12 is cleared to logic zero, then bits 0.13 and 0.8 will determine
`the link configuration regardless of the prior state ofthe link configuration and the Auto-Negotiation process.
`
`A PHY shall return a value of one in bit 0.9 until the Auto-Negotiation process has been initiated. The Auto-
`Negotiation process shall be initiated by setting bit 0.9 to a logic one. If Auto-Negotiation was completed
`prior to this bit being set, the process shall be reinitiated. If a PHY reports via bit 1.3 that it lacks the ability
`to perform Auto-Negotiation, then this bit will have no meaning, and should be written as zero. This bit is
`self-clearing. The Auto-Negotiation process shall not be affected by clearing this bit to logic zero.
`
`28.2.4.1.2 Mll status register
`
`The MII status register (register 1) includes information about all modes of operations supported by the
`Local Device’s PHY, the status ofAuto—Negotiation, and whether the Auto—Negotiation fimction is supported
`by the PHY or not. The definition for this register is provided in 22.2.4.2.
`
`When read as a logic one, bit 1.5 indicates that the Auto-Negotiation process has been completed, and that
`the contents of registers 4, 5, and 6 are valid. When read as a logic zero, bit 1.5 indicates that the Auto-Nego-
`tiation process has not been completed, and that the contents of registers 4, 5, and 6 are meaningless. A PHY
`shall return a value of zero in hit 1.5 if Auto-Negotiation is disabled by clearing bit 0.12. A PHY shall also
`return a value of zero in bit 1.5 if it lacks the ability to perform Auto-Negotiation.
`
`When read as logic one, bit 1.4 indicates that a remote fault condition has been detected. The type of fault as
`well as the criteria and method of fault detection is PHY specific. The Remote Fault bit shall be implemented
`with a latching fimction, such that the occurrence of a remote fault will cause the Remote Fault bit to
`become set and remain set until it is cleared. The Remote Fault bit shall be cleared each time register 1 is
`read via the management interface, and shall also be cleared by a PHY reset.
`
`When read as a one, bit 1.3 indicates that the PHY has the ability to perform Auto-Negotiation. When read as
`a logic zero, bit 1.3 indicates that the PHY lacks the ability to perfonn Auto-Negotiation.
`
`28.2.4.1 .3 Auto-Negotiation advertisement register (register 4) (RIW)
`
`This register contains the Advertised Ability of the PHY. (See table 28-2). The bit definition for the base
`page is defined in 28.2.1.2. On power—up, before Auto—Negotiation starts, this register shall have the follow-
`ing configuration: The Selector Field (4.4:0) is set to an appropriate code as specified in armex 28A. The
`Acknowledge bit (4.14) is set to logic zero. The Technology Ability Field (4.12:5) is set based on the values
`set in the M11 status register (register 1) (l.l5:11) or equivalent.
`
`Only the bits in the Technology Ability Field that represent the technologies supported by the Local Device
`may be set. Any of the Technology Ability Field bits that may be set can also be cleared by management
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`bit 1025
`
`
`
`Aerohive - Exhibit 1025
`0270
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`Table 28-2—Advertisement register bit definitions
`
`
`
`before a renegotiation. This can be used to enable management to Auto-Negotiate to an alternate common
`mode.
`
`The management entity may initiate renegotiation with the Link Partner using alternate abilities by setting
`the Selector Field (4.4:0) and Technology Ability Field (4.12:5) to indicate the preferred mode of operation
`and setting the Restart Auto—Negotiation bit (0.9) in the control register (register 0) to logic one.
`
`Any writes to this register prior to completion ofAuto—Negotiation as indicated by bit 1.5 should be followed
`by a renegotiation for the new values to be properly used for Auto—Negotiation. Once Auto—Negotiation has
`completed, this register value may be examined by software to determine the highest common denominator
`technology.
`
`28.2.4.1.4 Auto-Negotiation link partner ability register (register 5) (R0)
`
`All of the bits in the Auto—Negotiation link partner ability register are read only. A write to the Auto—Negoti-
`ation link partner ability register shall have no effect.
`
`This register contains the Advertised Ability of the Link Partner’s PHY. (See tables 28-3 and 28-4.) The bit
`definitions shall be a direct representation of the received Link Code Word (figure 28-7). Upon successful
`completion of Auto—Negotiation, status register (register 1) Auto—Negotiation Complete bit (1.5) shall be set
`to logic one. If the Next Page fimction is supported, the Auto—Negotiation link partner ability register may be
`used to store Link Partner Next Pages.
`
`Table 28-3—Link partner ability register bit definitions (Base Page)
`
`
`
`The values contained in this register are only guaranteed to be valid once Auto—Negotiation has successfully
`completed, as indicated by bit 1.5 or, if used with Next Page exchange, after the Page Received bit (6.1) has
`been set to logic one.
`
`This is anzggchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`bit 1025
`
`
`
`Aerohive - Exhibit 1025
`0271
`
`

`
`CSMAICD
`
`IEEE
`Std 802.3u-1995
`
`Table 28-4—Link partner ability register bit definitions (Next Page)
`
`Description
`
`See 28.2.3.4
`
`Next Page
`
`Acknowledge
`
`Message Page
`
`Acknowledge 2
`
`Toggle
`
`Message/Unfonnatted Code
`Field
`
`See 28.2.3.4
`
`See 28.2.3.4
`
`See 28.2.3.4
`
`See 28.2.3.4
`
`See 28.2.3.4
`
`NOTE—If this register is used to store Link Partner Next Pages, the previous value of this register is assumed to be
`stored by a management entity that needs the information overwritten by subsequent Link Partner Next Pages.
`
`28.2.4.1.5 Auto-Negotiation expansion register (register 6) (R0)
`
`All of the bits in the Auto-Negotiation expansion register are read only; a write to the Auto-Negotiation
`expansion register shall have no effect. (See table 28-5.)
`
`Table 28-5—Expansion register bit definitions
`
`Description
`
`Default
`
`Reserved
`
`Parallel Detection Fault
`
`Link Partner Next Page Able
`
`Next Page Able
`
`Page Received
`
`Write as zero, ignore on read
`
`l = A fault has been detected via the
`Parallel Detection function.
`0 = A fault has not been detected via the Par-
`allel Detection function.
`
`1 = Link Partner is Next Page able
`0 = Link Partner is not Next Page able
`
`l = Local Device is Next Page able
`0 = Local Device is not Next Page able
`
`1 = A New Page has been received
`0 = A New Page has not been received
`
`able
`
`Link Partner Auto-Negotia-
`tion Able
`
`1 = Link Partner is Auto-Negotiation able
`0 = Link Partner is not Auto-Negotiation
`
`Bits 6.15:5 are reserved for future Auto-Negotiation expansion.
`
`The Parallel Detection Fault bit (6.4) shall be set to logic one to indicate that zero or more than one of the
`NLP Receive Link Integrity Test
`function,
`IOOBASE-TX, or
`l00BASE-T4 PMAs have indicated
`link_status=READY when the autoneg_wait_timer expires. The Parallel Detection Fault bit shall be reset to
`logic zero on a read of the Auto-Negotiation expansion register (register 6).
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stanggrd.
`
`Aerohive - Exhibit 1025
`
`0272
`
`Aerohive - Exhibit 1025
`0272
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`The Link Partner Next Page Able bit (6.3) shall be set to logic one to indicate that the Link Partner supports
`the Next Page function. This bit shall be reset to logic zero to indicate that the Link Partner does not support
`the Next Page fimction.
`
`The Next Page Able bit (6.2) shall be set to logic one to indicate that the Local Device supports the Next
`Page function. The Next Page Able bit (6.2) shall be set to logic zero if the Next Page function is not sup-
`ported.
`
`The Page Received bit (6.1) shall be set to logic one to indicate that a new Link Code Word has been
`received and stored in the Auto-Negotiation link partner ability register. The Page Received bit shall be reset
`to logic zero on a read of the Auto-Negotiation expansion register (register 6).
`
`The Link Partner Auto-Negotiation Able bit (6.0) shall be set to logic one to indicate that the Link Partner is
`able to participate in the Auto-Negotiation function. This bit shall be reset to logic zero if the Link Partner is
`not Auto-Negotiation able.
`
`28.2.4.1.6 Auto-Negotiation Next Page transmit register (register 7) (RIW)
`
`The Auto-Negotiation Next Page Transmit register contains the Next Page Link Code Word to be transmitted
`when Next Page ability is supported. (See table 28-6.) The contents are defined in 28.2.3.4. On power-up,
`this register shall contain the default value of 2001H, which represents a Message Page with the Message
`Code set to Null Message. This value may be replaced by any valid Next Page Message Code that the device
`wishes to transmit. Writing to this register shall set mr_next_page_loaded to true.
`
`Table 28-6—Next Page transmit register bit definitions
`
`
`
`28.2.4.1.7 State diagram variable to Mll register mapping
`
`The state diagrams of figures 28-14 to 28-17 generate and accept variables of the form “mr_x”, where x is an
`individual signal name. These variables comprise a management interface that may be connected to the MII
`management function or other equivalent fimction. Table 28-7 describes how the MII registers map to the
`management function interface signals.
`
`28.2.4.2 Auto-Negotiation managed object class
`
`The Auto-Negotiation Managed Object Class is defined in clause 30.
`
`This is anzggrchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`bit 1025
`
`
`
`Aerohive - Exhibit 1025
`0273
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`Table 28-7—State diagram variable to Mll register mapping
`
`28.2.5 Absence of management function
`
`In the absence of any management function, the advertised abilities shall be provided through a logical
`equivalent of n1r_adv_ability[l6:l]. A device shall comply with all Next Page function requirements, includ-
`ing the provision of the rnr_np_able, mr_lp_n _able, and mr_next_page_loaded variables (or their logical
`equivalents), in order to permit the NP bit to be set to logic one in the transmitted Link Code Word.
`
`NOTE—Storage of a valid base Link Code Word is required to prevent a deadlock situation where negotiation must start
`again while Next Pages are being transmitted. If a shared transmit register were used, then renegotiation could not occur
`when Next Pages were being transmitted because the base Link Code Word would not be available. This requirement can
`be met using a number of different implementations, including use of temporary registers or register stacks.
`
`28.2.6 Technology-Dependent Interface
`
`The Technology-Dependent Interface is the communication mechanism between each technology’s PMA
`and the Auto-Negotiation function. Auto-Negotiation can support multiple technologies, all of which need
`not be implemented in a given device. Each of these technologies may utilize its own technology-dependent
`link integrity test fimction.
`
`28.2.6.1 PMA_LlNK.indicate
`
`This primitive is generated by the PMA to indicate the status of the underlying medium. The purpose of this
`primitive is to give the PCS, repeater client, or Auto-Negotiation function a means of determining the valid-
`ity of received code elements.
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`bit 1025
`
`
`
`Aerohive - Exhibit 1025
`0274
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`28.2.6.1.1 Semantics of the service primitive
`
`PMA_LINK.indicate(link_status)
`
`The link_status parameter shall assume one of three values: READY, OK, or FAIL, indicating whether the
`underlying receive channel is intact and ready to be enabled (READY), intact and enabled (OK), or not
`intact
`(FAIL). When link_status=FAIL or
`link_status=READY,
`the PMA_CARRIER.indicate and
`PMA_UNITDATA.indicate primitives are undefined.
`
`28.2.6.1 .2 When generated
`
`A technology-dependent PMA and the NLP Receive Link Integrity Test state diagram (figure 28-17) shall
`generate this primitive to indicate the value of link_status.
`
`28.2.6.1.3 Effect of receipt
`
`The effect of receipt of this primitive shall be governed by the state diagrams of figure 28-16.
`
`28.2.6.2 PMA_LlNK.request
`
`This primitive is generated by Auto-Negotiation to allow it to enable and disable operation of the PMA.
`
`28.2.6.2.1 Semantics of the service primitive
`
`PMA_LINK request(link_control)
`
`The link_control parameter shall assume one of three values: SCAN_FOR_CARRIER, DISABLE, or
`ENABLE.
`
`The link_control=SCAN_FOR_CARRIER mode is used by the Auto-Negotiation fimction prior to receiving
`any FLP Bursts or link_status=READY indications. During this mode, the PMA shall search for carrier and
`report link_status=READY when carrier is received, but no other actions shall be enabled.
`
`The link_control=DISABLE mode shall be used by the Auto-Negotiation fLlI1Ctl01‘l to disable PMA processing.
`
`The lir1k_control=ENABLE mode shall be used by Auto-Negotiation to turn control over to a single PMA
`for all normal processing functions.
`
`28.2.6.2.2 When generated
`
`The Auto-Negotiation function shall generate this primitive to indicate to the PHY how to respond, in accor-
`dance with the state diagrams of figures 28-15 and 28-16.
`
`if the Auto-Negotiation function is enabled (mr_autoneg_enable=true) the
`Upon power-on or reset,
`PMA_LINK request(DISABLE) message shall be issued to all technology-dependent PMAs. IfAuto-Nego-
`tiation is disabled at any time including at power-on or reset, the state of PMA_LlNK.request(link_control)
`is implementation dependent.
`
`28.2.6.2.3 Effect of receipt
`
`The effect of receipt of this primitive shall be governed by the NLP Receive Link Integrity Test state diagram
`(figure 28-17) and the receiving technology-dependent link integrity test function, based on the intent speci-
`fied in the primitive semantics.
`
`This is anzgxrchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`bit 1025
`
`
`
`Aerohive - Exhibit 1025
`0275
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`28.3 State diagrams and variable definitions
`
`The notation used in the state diagrams (figures 28-14 to 28-17) follows the conventions in 21.5. State dia-
`gram variables follow the conventions of 21.5.2 except when the variable has a default value. Variables in a
`state diagram with default values evaluate to the Variable default in each state where the variable value is not
`explicitly set. Variables using the “mr_x” notation do not have state diagram defaults; however, their appro-
`priate initialization conditions when mapped to the M11 interface are covered in 28.2.4 and 22.2.4. The vari-
`ables, timers, and counters used in the state diagrams are defined in 28.3, 14.2.3, and 28.2.6.
`
`Auto-Negotiation shall implement the Transmit state diagram, Receive state diagram, Arbitration state dia-
`gram, and NLP Receive Link Integrity Test state diagram as depicted in 28.3. Additional requirements to
`these state diagrams are made in the respective fimctional requirements sections. Options to these state dia-
`grams clearly stated as such in the fimctional requirements sections or state diagrams shall be allowed. In the
`case of any ambiguity between stated requirements and the state diagrams, the state diagrams shall take pre-
`cedence.
`
`Management Interface
`
`
`
`16
`
`
`
`
`
`
`
`
`
`comp|ete_ack
`
`1ransmit_ability
`
`fl -
`
`link ood
`
`ack_finished
`
`tx_link_code_word[16:1]
`
`16
`
`PMA_LlNK.indicate
`PMA_LlNK.request
`
`(|ink_status)
`(|ink_contro|)
`
`
`TD_AUTON EG
`
`
`
`Technology-
`Dependent
`Interface
`
`- - - - - -
`
`28.3.1 State diagram variables
`
`A variable with “_[x]” appended to the end of the variable name indicates a variable or set of variables as
`defined by “x”. “x” may be as follows:
`
`all;
`
`represents all specific technology-dependent PMAs supported in the Local Device and the NLP
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`bit 1025
`
`
`
`Aerohive - Exhibit 1025
`0276
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`Receive Link Integrity Test state diagram.
`
`HCD;
`
`represents the single technology-dependent PMA chosen by Auto-Negotiation as the highest
`common denominator technology through the Priority Resolution or Parallel Detection
`function. To select 1OBASE—T, LIT is used instead of NLP to enable the full 10BASE—T Link
`Integrity Test function state diagram.
`
`notHCD;
`
`represents all technology-dependent PMAs not chosen by Auto-Negotiation as the highest
`common denominator technology through the Priority Resolution or Parallel Detection
`function.
`
`TX;
`
`T4;
`
`NLP;
`
`PD;
`
`LIT;
`
`represents that the IOOBASE-TX PMA is the signal source.
`
`represents that the 100BASE-T4 PMA is the signal source.
`
`represents that the NLP Receive Link Integrity Test function is the signal source.
`
`represents all of the following that are present: l00BASE—TX PMA, 100BASE-T4 PMA, and
`the NLP Receive Link Integrity Test state diagram.
`
`represents the 10BASE—T Link Integrity Test function state diagram is the signal source or
`destination.
`
`Variables with [16:1] appended to the end of the variable name indicate arrays that can be directly mapped to
`16-bit registers. For these variables, “[x]” indexes an element or set of elements in the array, where “[x]”
`may be as follows:
`
`— Any integer.
`— Any variable that takes on integer values.
`— NP; represents the index of the Next Page bit.
`— ACK; represents the index of the Acknowledge bit.
`— RF; represents the index of the Remote Fault bit.
`
`Variables of the form “mr_x”, where x is a label, comprise a management interface that is intended to be
`connected to the M11 Management function. However, an implementation-specific management interface
`may provide the control and status function of these bits.
`
`abi1ity_match
`Indicates that three consecutive Link Code Words match, ignoring the Acknowledge bit. Three
`consecutive words are any three words received one after the other, regardless ofwhether the word
`has already been used in a word—match comparison or not.
`
`Values:
`
`false; three matching consecutive Link Code Words have not been received, ignoring
`the Acknowledge bit (default).
`true; three matching consecutive Link Code Words have been received, ignoring the
`Acknowledge bit.
`
`NOTE—This variable is set by this variable definition; it is not set explicitly in the state diagrams.
`
`ack_finished
`Status indicating that the final remaining_ack_cnt Link Code Words with the Ack bit set have been
`transmitted.
`
`Values:
`
`false; more Link Code Words with the Ack bit set to logic one must be transmitted.
`true; all remaining Link Code Words with the Ack bit set to logic one have been
`transmitted.
`
`acknowledge_match
`Indicates that three consecutive Link Code Words match and have the Acknowledge bit set. Three
`consecutive words are any three words received one after the other, regardless ofwhether the word
`has already been used m a word match comparison or not.
`
`Values:
`
`false; three matching and consecutive Link Code Words have not been received with the
`
`This is arizggchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`bit 1025
`
`
`
`Aerohive - Exhibit 1025
`0277
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`Acknowledge bit set (default).
`true; three matching and consecutive Link Code Words have been received with the
`Acknowledge bit set.
`
`NOTE—This variable is set by this variable definition; it is not set explicitly in the state diagrams.
`
`base_page
`Status indicating that the page currently being transmitted by Auto—Negotiation is the initial Link
`Code Word encoding used to communicate the device’s abilities.
`
`Values:
`
`false; a page other than base Link Code Word is being transmitted.
`true; the base Link Code Word is being transmitted.
`
`complete_ack
`Controls the counting of transmitted Link Code Words that have their Aclmowledge bit set.
`
`Values:
`
`false; transmitted Link Code Words with the Acknowledge bit set are not counted
`(default).
`true; transmitted Link Code Words with the Acknowledge bit set are counted.
`
`consistency_match
`Indicates that the Link Code Word that caused ability_match to be set is the same as the Link Code
`Word that caused acknowledge_match to be set.
`
`Values:
`
`false; the Link Code Word that caused ability_match to be set is not the same as the Link
`Code Word that caused acknowledge_match to be set, ignoring the Acknowledge bit
`value.
`
`true; the Link Code Word that caused ability match to be set is the same as the Link
`Code Word that caused acknowledge_match t_o be set, independent ofthe Acknowledge
`bit value.
`
`NOTE—This variable is set by this variable definition; it is not set explicitly in the state diagrams.
`
`desire_np
`Status indicating that the Local Device desires to engage in Next Page exchange. This information
`comes from the setting of the NP bit in the base Link Code Word stored in the Auto—Negotiation
`advertisement register (register 4).
`
`Values:
`
`false; Next Page exchange is not desired.
`true; Next Page exchange is desired.
`
`flp_link_good
`Indicates that Auto—Negotiation has completed.
`
`Values:
`
`false; negotiation is in progress (default).
`true; negotiation is complete, forcing the Transmit and Receive functions to IDLE.
`
`flp_receive_id1e
`Indicates that the Receive state diagram is in the IDLE, LINK PULSE DETECT, or LINK PULSE
`COUNT state.
`
`Values:
`
`false; the Receive state diagram is not in the IDLE, LINK PULSE DETECT, or LINK
`PULSE COUNT state (default).
`true; the Receive state diagram is in the IDLE, LINK PULSE DETECT, or LINK
`PULSE COUNT state.
`
`link_control
`This variable is defined in 28.2.6.2.l.
`
`link_status
`This variable is defined in 28.2.6.l.1.
`
`linkpulse
`Indicates that a valid Link Pulse as transmitted in compliance with figure 14-12 has been received.
`
`Values:
`
`false; linkpulse is set to false afier any Receive State Diagram state transition (default).
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`bit 1025
`
`
`
`Aerohive - Exhibit 1025
`0278
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`true; linkpulse is set to true when a valid Link Pulse is received.
`
`mr_autoneg_complete
`Status indicating Whether Auto-Negotiation has completed or not.
`
`Values:
`
`false; Auto-Negotiation has not completed.
`true; Auto-Negotiation has completed.
`
`mr_autoneg_enab1e
`Controls the enabling and disabling of the Auto-Negotiation function.
`
`Values:
`
`false; Auto-Negotiation is disabled.
`true; Auto-Negotiation is enabled.
`
`mr_adv_abi1ity[ 1 6: 1]
`A 16-bit array that contains the Advertised Abilities Link Code Word.
`For each element within the array:
`
`Values: Zero; data bit is logical zero.
`One; data bit is logical one.
`
`mr_lp_adv_ability[ 1 6: 1 ]
`A 16-bit array that contains the Link Partner’s Advertised Abilities Link Code Word.
`For each element within the array:
`
`Values: Zero; data bit is logical zero.
`One; data bit is logical one.
`
`mr_lp_np_able
`Status indicating whether the Link Partner supports Next Page exchange.
`
`Values:
`
`false; the Link Partner does not support Next Page exchange.
`true; the Link Partner supports Next Page exchange.
`
`mr_np_able
`Status indicating whether the Local Device supports Next Page exchange.
`
`Values:
`
`false; the Local Device does not support Next Page exchange.
`true; the Local Device supports Next Page exchange.
`
`mr_lp_autoneg_able
`Status indicating whether the Link Partner supports Auto-Negotiation.
`
`Values:
`
`false; the Link Partner does not support Auto-Negotiation.
`true; the Link Parmer supports Auto-Negotiation.
`
`mr_main_reset
`Controls the resetting of the Auto-Negotiation state diagrams.
`
`Values:
`
`false; do not reset the Auto-Negotiation state diagrams.
`true; reset the Auto-Negotiation state diagrams.
`
`mr_next_page_loaded
`Status indicating whether a new page has been loaded into the Auto-Negotiation Next Page
`Transmit register (register 7).
`
`Values:
`
`false; a New Page has not been loaded.
`true; a New Page has been loaded.
`
`mr_np_1x[16:1]
`A 16-bit array that contains the new Next Page to transmit.
`For each element within the array:
`
`Values: Zero; data bit is logical zero.
`One; data bit is logical one.
`
`This is anzggchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`bit 1025
`
`
`
`Aerohive - Exhibit 1025
`0279
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`mr_page_rx
`Status indicating whether a New Page has been received. A New Page has been successfully
`received when acl<nowledge_match=true and consistency_rnatch=true and the Link Code Word
`has been written to rr1r_lp_adv_ability[l6: 1].
`
`Values:
`
`false; a New Page has not been received.
`true; a New Page has been received.
`
`mrJ)arallel_detection_fault
`Error condition indicating that while performing Parallel Detection, either
`flp_receive_idle = false, or zero or more than one of the following indications were present when
`the autoneg_wait_timer expired. This signal is cleared on read of the Auto-Negotiaion expansion
`register.
`
`1) link_status_ [NLP] = READY
`2) link_status_[TX] = READY
`3) link_status_[T4] = READY
`
`Values:
`
`false; Exactly one of the above three indications was true when the
`autoneg_wait_tirner expired, and flp_receive_idle = true.
`true; either zero or more than one of the above three indications was true when the
`autoneg_wait_tirner expired, or flp_receive_idle = false.
`
`mr_restart_negotiation
`Controls the entrance to the TRANSMIT DISABLE state to break the link before Auto-
`
`Negotiation is allowed to renegotiate via management control.
`
`Values:
`
`false; renegotiation is not taking place.
`true; renegotiation is started.
`
`power_on
`Condition that is true until such time as the power supply for the device that contains the Auto-
`Negotiation state diagrams has reached the operating region or the device has low power mode set
`via M11 control register bit 0.11.
`
`Values:
`
`false; the device is completely powered (default).
`true; the device has not been completely powered.
`
`rx_link_code_word[ 1 6: 1 ]
`A 16-bit array that contains the data bits to be received from an FLP Burst.
`For each element within the array:
`
`Values:
`
`zero; data bit is a logical zero.
`one; data bit is a logical one.
`
`single_link_ready
`Status indicating that flp_receive_idle = true and only one the ofthe following indications is being
`received:
`
`1) link_status_[NLP] = READY
`2) link_status_[TX] = READY
`3) link_status_[T4] = READY
`
`Values:
`
`false; either zero or more than one of the above three indications are true or
`flp_receive_idle = false.
`true; Exactly one of the above three indications is true and flp_receive_idle = true.
`
`NOTE—This variable is set by this variable definition; it is not set explicitly in the state diagrams.
`
`TD_AUTONEG
`Controls the signal sent by Auto-Negotiation on the TD_AUTONEG circuit.
`
`Values:
`
`idle; Auto-Negotiation prevents transmission of all link pulses on the MDI.
`link_test_pulse; Auto-Negotiation causes a single link pulse as defined by figure 14-12
`to be transmitted on the MDI.
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`bit 1025
`
`
`
`Aerohive - Exhibit 1025
`0280
`
`

`
`IEEE
`Std 802.3u-1995
`
`toggle_rx
`
`SUPPLEMENT TO 802.3:
`
`Flag to keep track of the state of the Link Partner’s Toggle bit.
`
`Values:
`
`0; Link Par111er’s Toggle bit equals logic zero.
`1; Link Part11er’s Toggle bit equals logic one.
`
`toggle_tx
`Flag to keep track of the state of the Local Device’s Toggle bit.
`
`Values:
`
`0; Local Device’s Toggle bit equals logic zero.
`1; Local Device’s Toggle bit equals logic one.
`
`transmit_ability
`Controls the transmission of the Link Code Word containing tx_link_code_word[16:l].
`
`Values:
`
`false; any transmission of tx_link_code_word[16: 1] is halted (default).
`true; the transmit state diagram begins sending tx_link_code_word[16: 1].
`
`transmit_ack
`Controls the setting of the Acknowledge bit in the tx_link_code_word[16: 1] to be transmitted.
`
`Values:
`
`false; sets the Acknowledge bit in the transmitted tx_link_code_word[16:l] to a logic
`zero (default).
`true; sets the Acknowledge bit in the transmitted tx_link_code_word[16:l] to a logic
`one.
`
`transmit_disable
`Controls the transmission of tx_link_code_word[l6: 1].
`
`Values:
`
`false; tx_link_code_word[16: 1] transmission is allowed (default).
`true; tx_link_code_word[16: 1] transmission is halted.
`
`tx_1ink_code_word[1 6: 1]
`A 16-bit array that contains the data bits to be transmitted in an FLP Burst. This array may be
`loaded from mr_adv_ability or rnr_np_tx.
`For each element within the array:
`
`Values: Zero; data bit is logical zero.
`One; data bit is logical one.
`
`28.3.2 State diagram timers
`
`All timers operate in the manner described in 14.2.3.2.
`
`autoneg_wait_timer
`Timer for the a