Important: if this rebase instead contains *only bug fixes,* or *only enhancements*, select the correct option from the Doc Type drop-down list.
Rebase package(s) to version:
1.4 (git snapshot from 20140318)
Highlights, important fixes, or notable enhancements:
Added an adaptive servo based on linear regression (unlike PI servo, it doesn't need to be configured for good performance), included improvements for 802.1AS clocks, fixed bugs in delay measurement, added new configuration options, and other improvements and bugfixes.
Description of problem:
This is a proposal to rebase linuxptp to the new 1.4 release.
It fixes several important bugs and adds some new useful features. It fixes all currently open RHEL6 bugs for linuxptp (bug #1019121, bug #1016356, bug #1011022, bug #1004996).
Announcement with changelog:
(In reply to Miroslav Lichvar from comment #0)
> Description of problem:
> This is a proposal to rebase linuxptp to the new 1.4 release.
> It fixes several important bugs and adds some new useful features. It fixes
> all currently open RHEL6 bugs for linuxptp (bug #1019121, bug #1016356, bug
> #1011022, bug #1004996).
> Announcement with changelog:
It seems the changelog cannot be opened because of 403.
BTW, do you have any suggestions what kind of tests we should do specifically for the update?
(In reply to Jimmy Pan from comment #1)
> It seems the changelog cannot be opened because of 403.
Here is a mirror: http://thread.gmane.org/gmane.comp.linux.ptp.devel/1784
> BTW, do you have any suggestions what kind of tests we should do
> specifically for the update?
Beside testing of the other bugs filed for linuxptp, which will be fixed by this rebase, I think it would be nice to test the new fast slewing of the system clock (10% instead of 500ppm) with ptp4l and SW time stamping or phc2sys.
I'm considering to rebase to a post-1.4 git snapshot (2b099cf) to include the new adaptive linreg servo.
BTW, I'll include in the package linuxptp-testsuite with clknetsim and run it in rpm %check to have better testing coverage.
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.