Changes between Version 3 and Version 4 of timesync

12/06/2018 07:15:06 PM (5 years ago)
Cale Collins

added octeon tx section


  • timesync

    v3 v4  
    97           <div class="trac-modifiedby">
    98             <span><a href="/wiki/linux/timesync?action=diff&amp;version=2" title="Version 2 by tharvey: added example usage">Last modified</a> <a class="timeline" href="/timeline?from=2015-08-27T16%3A41%3A56-07%3A00&amp;precision=second" title="See timeline at 08/27/15 16:41:56">2 years ago</a></span>
    99             <span class="trac-print">Last modified on 08/27/15 16:41:56</span>
    100           </div>
    103       </div>
    106     </div>
    107     <div id="altlinks">
    108       <h3>Download in other formats:</h3>
    109       <ul>
    110         <li class="last first">
    111           <a rel="nofollow" href="/wiki/linux/timesync?format=txt">Plain Text</a>
    112         </li>
    113       </ul>
    114     </div>
    115     </div>
    116     <div id="footer" lang="en" xml:lang="en"><hr />
    117       <a id="tracpowered" href=""><img src="/chrome/common/trac_logo_mini.png" height="30" width="107" alt="Trac Powered" /></a>
    118       <p class="left">Powered by <a href="/about"><strong>Trac 1.0</strong></a><br />
    119         By <a href="">Edgewall Software</a>.</p>
    120       <p class="right">Visit the Trac open source project at<br /><a href=""></a></p>
    121     </div>
     97= Octeon TX IEEE 1588
    123 }}}
     99From CN80xx refrence manual:
     101The CN80XX hardware supports very accurate timestamping in the PTP, BGX, GTI,
     102and NIC blocks. This timestamping is suitable for use in IEEE 1588 Precision Time
     103Protocol (PTP) or other purposes.
     105The CN80XX outbound timestamping hardware captures timestamps, but cannot
     106insert the timestamp into any outgoing packets. Using IEEE 1588 vernacular, this
     107means that the CN80XX outbound timestamping hardware is most useful when
     108implementing a two-step clock, not a one-step clock, for PTP event messages sent
     109from CN80XX. After the hardware captures the timestamp for the outgoing 1588
     110event message and delivers it to software, the 1588 software running on the CN80XX
     111may need to send the timestamp to required recipients in a subsequent 1588 general
     112message as a second step.
     114NIC has no specific mode supporting PTP timestamping, but contains a number of
     115features to compensate for the PTP timestamp introduced by BGX when it is
     117When BGX is in the receive-timestamp mode, NIC receives the timestamp plus
     118packet from the BGX. NIC packet parsing is able to skip over the received
     119timestamps (NIC_PF_PKIND(0..15)_CFG[HDR_SL]). NIC MAXERR, MINERR, and
     120LENERR checks can compensate for the additional header, since the MAXERR and
     121MINERR byte counts are programmable, and the programmed value can easily be
     122increased by 8. The LENERR check already compensates based on the skip value.
     123NIC makes the timestamp available for software with every packet. The timestamp
     124can be present in the completion-queue entry and/or the receive buffer in L2/DRAM
     125for software, depending on NIC configuration. The software will likely use the
     126timestamp when IEEE 1588 event messages arrive. For other packets, the software
     127may choose to discard or ignore the timestamp that is present with every packet in
     128this mode.
     130[[Image(cavium-octeon-tx-block-diagram.jpg, width=600)]]