Want dynamic tx-eq tuning
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- rust
- Domain
- networking
Research direction
Start with dpd/misc/xcvr_defaults.csv and trace how Dendrite uses these transceiver transmit-equalization defaults. Determine whether the transceiver exposes feedback for tx loss of lock or signal, then define and validate a dynamic tuning approach that preserves explicit operator overrides and replaces static values with initial conditions.
Written by the indexing model from the issue text.
Description
We have a static set of default values that we ship with Dendrite for determining what the transmit equalization settings should be for a given transceiver. However, experience has shown that these do not always work.
For transceivers that do not have explicit tx-eq settings override from the operator, we should use these values as initial conditions rather than a static specification. When a link does not come up due to tx loss of lock or tx loss of signal, we should have an algorithm to tune the link dynamically. Ideally this could be a feedback-based control if we can get said feedback from the transceiver module. We had an issue recently where I manually did this based on intuition on how the tx-eq circuit works and the fact that we were seeing loss of lock. But to the extent possible this should be automatic based FIR circuit models and feedback based observations.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 3
- Avg merge
- 10h 45m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from oxidecomputer/dendrite
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
oxidecomputer/dendrite#384 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
oxidecomputer/dendrite#375 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
oxidecomputer/dendrite#369 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
oxidecomputer/dendrite#368 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
oxidecomputer/dendrite#359 · 1 comment ·
Maintainers usually reply within 1 day
All issues in oxidecomputer/dendrite
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
aws-samples/sample-pacer#76 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
axodotdev/cargo-dist#2523 ·
Maintainers usually reply within 2 days