Bug 1359311
| Summary: | linuxptp rebase | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jonathan Edwards <joedward> |
| Component: | linuxptp | Assignee: | Miroslav Lichvar <mlichvar> |
| Status: | CLOSED ERRATA | QA Contact: | Qiao Zhao <qzhao> |
| Severity: | medium | Docs Contact: | Lenka Špačková <lkuprova> |
| Priority: | high | ||
| Version: | 7.3 | CC: | atragler, cye, thozza |
| Target Milestone: | rc | Keywords: | Rebase |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | linuxptp-1.8-1.el7 | Doc Type: | Release Note |
| Doc Text: |
_linuxptp_ rebased to version 1.8
The linuxptp packages have been upgraded to upstream version 1.8, which provides a number of bug fixes and enhancements over the previous version. Notable enhancements include:
* Added support for hybrid end-to-end (E2E) delay measurements using unicast messages to reduce network traffic in large networks.
* Added support for running a boundary clock (BC) using independent Precision Time Protocol (PTP) hardware clocks.
* Added options to configure Time to Live (TTL) and Differentiated Services Code Point (DSCP) of PTP messages.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 20:31:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1298243, 1380362, 1393869, 1411886 | ||
|
Description
Jonathan Edwards
2016-07-22 18:58:27 UTC
Upstream recently released 1.7. I think we should try to rebase to that. There were some bugfixes and also some minor improvements in timemaster. linuxptp 1.8 will be probably released in the next few weeks. We should rebase to that. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1918 |