`port_settings_apply` does not update tx-eq settings
Maintainers usually reply within 1 day
@rcgoodfellow is already working on this.
Since Sep 24, 2025.
Assessment
This issue has not been assessed yet.
Description
First noticed debugging #104
If we create a link with port_settings_apply and then attempt to update tx-eq settings on a subsequent call, nothing happens.
Settings do not change for existing link
root@oxz_switch1:~# ./swadm link apply --link qsfp11/0 --tag muffins --speed 100g --fec rs
root@oxz_switch1:~# ./swadm link sd get tx-eq qsfp11/0
lane 0 lane 1 lane 2 lane 3
pre2 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
pre1 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
main 26 ( 26) 26 ( 26) 26 ( 26) 26 ( 26)
post1 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
post2 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
root@oxz_switch1:~# ./swadm link apply --link qsfp11/0 --tag muffins --speed 100g --fec rs --main 7
root@oxz_switch1:~# ./swadm link sd get tx-eq qsfp11/0
lane 0 lane 1 lane 2 lane 3
pre2 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
pre1 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
main 26 ( 26) 26 ( 26) 26 ( 26) 26 ( 26)
post1 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
post2 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
But if you delete the link and create it with a particular tx-eq cursor value from the beginning, that takes
root@oxz_switch1:~# ./swadm link del qsfp11/0
root@oxz_switch1:~# ./swadm link apply --link qsfp11/0 --tag muffins --speed 100g --fec rs --main 7
root@oxz_switch1:~# ./swadm link sd get tx-eq qsfp11/0
lane 0 lane 1 lane 2 lane 3
pre2 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
pre1 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
main 7 ( 7) 7 ( 7) 7 ( 7) 7 ( 7)
post1 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
post2 0 ( 0) 0 ( 0) 0 ( 0) 0 ( 0)
- Dominant language
- Rust
- Stars
- 21
- Forks
- 3
- Avg merge
- 8h 29m
- 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 2/5 1-3 hours Newbie friendliness 78/100
oxidecomputer/dendrite#380 ·
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 ·
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
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stackabletech/kafka-operator#1033 · 1 comment ·
Maintainers usually reply within 1 day
-
bug good first issue needs testing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
farion1231/cc-switch#7744 · 1 comment ·
Maintainers usually reply within 1 day
-
datafusion
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/iceberg-rust#3297 ·
Maintainers usually reply within 1 day