Releases: slaclab/lcls2-pgp-fw-lib
Releases · slaclab/lcls2-pgp-fw-lib
Patch Release v5.10.1
Description
- Update lcls2_pgp_ci.yml
- Increasing NUM_DETECTORS_G range from 4 to 8
- whitespace removal
Full Changelog: v5.10.0...v5.10.1
Minor Release v5.10.0
Description
Full Changelog: v5.9.2...v5.10.0
Patch Release v5.9.2
Patch Release v5.9.1
Pull Requests Since v5.9.0
Pull Request Details
Minor Release v5.9.0
v5.8.0
Description
Full Changelog: v5.7.0...v5.8.0
v5.6.0
Description
Full Changelog: v5.5.1...v5.6.0
Patch Release v5.5.1
Description
Full Changelog: v5.5.0...v5.5.1
Minor Release v5.4.0
Pull Requests Since v5.3.0
Unlabeled
- #45 - Release Candidate v5.4.0
Pull Request Details
Release Candidate v5.4.0
Author: | Larry Ruckman [email protected] |
Date: | Wed Sep 8 14:22:29 2021 -0700 |
Pull: | #45 (18 additions, 13 deletions, 3 files changed) |
Branch: | slaclab/KCU1500-ref-clk |
Notes:
Description
- using KCU1500.userClk156 (instead of userClk25) to create the 371 MHz clock
Minor Release v5.3.0
Pull Requests Since v5.2.2
Unlabeled
Pull Request Details
adding GTGREFCLK Interface Option to LCLS-II/gthUltraScale
Author: | Larry Ruckman [email protected] |
Date: | Thu Aug 26 10:23:49 2021 -0700 |
Pull: | #43 (22 additions, 15 deletions, 3 files changed) |
Branch: | slaclab/ruckman-testing |
Notes:
Description
- adding GTGREFCLK Interface Option to LCLS-II/gthUltraScale
- This update seems to resolve the TX link issue.
- The KCU1500's 371 MHz is derived from MMCM. You can't use the GT clock network without jitter issues. But appears to be less of an issue (or none at all) if you use GTGREFCLK port instead
Release Candidate v5.3.0
Author: | Larry Ruckman [email protected] |
Date: | Thu Aug 26 10:33:31 2021 -0700 |
Pull: | #44 (132 additions, 6 deletions, 4 files changed) |
Branch: | slaclab/pre-release |
Issues: | #43 |
Notes:
Description
- updating lcls-timing-core submodule lock to be >=
v3.6.0
- #43