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

Incorrect value of RSP_CAPABILITIES_VERSION constant #10

Open
VVakko opened this issue Dec 9, 2022 · 0 comments
Open

Incorrect value of RSP_CAPABILITIES_VERSION constant #10

VVakko opened this issue Dec 9, 2022 · 0 comments

Comments

@VVakko
Copy link

VVakko commented Dec 9, 2022

When you made significant changes to the rsp_extended_capabilities_t structure (adding the antenna_input_count, third_antenna_name, third_antenna_freq_limit fields and shifting the tuner_count, ifgr_min, ifgr_max fields), you forgot to increase the version number in the SP_CAPABILITIES_VERSION constant. Is it possible to increase the version number now?
I am currently writing a small plugin https://user-images.githubusercontent.com/26070386/203162300-0457e69e-9928-4246-a6fb-1c3cba102c19.png , universal for rtl_tcp, hackrf_tcp, rsp_tcp and I don't understand yet how to determine which version of rsp_tcp is on the other side. The 2nd version of rdp_tcp (which is quite popular) has tuner_count located in one place of the structure, and the 3rd version of rdp_tcp has the name of the 3rd antenna port there. Changing RSP_CAPABILITIES_VERSION in the 3rd version of rdp_tcp would solve the ambiguity problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant