Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | n320: Improve comments regarding low band | Martin Braun | 2022-06-10 | 1 | -0/+6 |
| | | | | | The N320 code include some constants that were either unused or incorrect. This clarifies the lowband frequency. | ||||
* | uhd: Harmonize fuzzy frequency comparisons | Martin Braun | 2022-02-04 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Throughout UHD, we often do floating-point comparisons for frequency ranges that require resilience to floating point rounding errors. Most of the time the checks look like this: ```cpp if (fp_compare_epsilon<double>(freq) > boundary) { // ... } ``` The exception is the N320 daughterboard control, which uses a custom epsilon: ```cpp if (fp_compare_epsilon<double>(freq, RHODIUM_FREQ_COMPARE_EPSILON) > boundary) { // ... } ``` This was, for the most part, not by design, but because authors simply didn't think about which epsilon value was appropriate for the frequency comparison. This was complicated by the fact that fp_compare_epsilon previously had some issues. This patch introduces FREQ_COMPARE_EPSILON, which is a sensible default value for fp_compare_epsilon when doing frequency comparisons (note that fp_compare_delta already had such a value). Also, it introduces freq_compare_epsilon(x), which is a shorthand for fp_compare_epsilon<double>(x, FREQ_COMPARE_EPSILON). We then replace all occurrences of fp_compare_epsilon<double> which are specific to frequency checks with freq_compare_epsilon. | ||||
* | rh: Remove unused constant | Martin Braun | 2021-03-04 | 1 | -1/+0 |
| | | | | This fixes a clang warning. | ||||
* | uhd: Apply clang-format against all .cpp and .hpp files in host/ | Martin Braun | 2020-03-03 | 1 | -51/+50 |
| | | | | | Note: template_lvbitx.{cpp,hpp} need to be excluded from the list of files that clang-format gets applied against. | ||||
* | x300/mpmd: Port all RFNoC devices to the new RFNoC framework | Martin Braun | 2019-11-26 | 1 | -11/+11 |
| | | | | | | | Co-Authored-By: Alex Williams <alex.williams@ni.com> Co-Authored-By: Sugandha Gupta <sugandha.gupta@ettus.com> Co-Authored-By: Brent Stapleton <brent.stapleton@ettus.com> Co-Authored-By: Ciro Nishiguchi <ciro.nishiguchi@ni.com> | ||||
* | rh: add support for rhodium devices | Mark Meserve | 2018-10-25 | 1 | -0/+135 |
Co-authored-by: Humberto Jimenez <humberto.jimenez@ni.com> Co-authored-by: Alex Williams <alex.williams@ni.com> Co-authored-by: Derek Kozel <derek.kozel@ni.com> |