Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insufficient ticker nodes for vendor implementations #25067

Closed
mtpr-ot opened this issue May 7, 2020 · 0 comments · Fixed by #25066
Closed

Insufficient ticker nodes for vendor implementations #25067

mtpr-ot opened this issue May 7, 2020 · 0 comments · Fixed by #25066
Assignees
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug
Milestone

Comments

@mtpr-ot
Copy link
Collaborator

mtpr-ot commented May 7, 2020

Vendors need to be able to reserve ticker nodes for proprietary LL implementations. There is currently no way of achieving this. Dynamically reusing ticker ids reserved by ULL may cause erratic behavior.

Impact
Reusing other ticker ids dyamically is not a safe way to implement features, as usage or rules may change in upstream code. A number of user- or vendor ticker nodes should be configurable.

@mtpr-ot mtpr-ot added the bug The issue is a bug, or the PR is fixing a bug label May 7, 2020
@mtpr-ot mtpr-ot added this to the v2.2.1 milestone May 7, 2020
@mtpr-ot mtpr-ot self-assigned this May 7, 2020
@aescolar aescolar added area: Bluetooth priority: medium Medium impact/importance bug has-pr labels May 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants