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

Remote device should probably return remote:driver= and remote= to work with make #11

Closed
cjcliffe opened this issue Oct 5, 2015 · 3 comments

Comments

@cjcliffe
Copy link
Contributor

cjcliffe commented Oct 5, 2015

When querying the device remotely (RTLSDR at least, I may have missed something in the module?), the only way I know it's an rtlsdr is by checking known parameters and the 'rtl' index key. It would be handy to automatically return the remote:driver and remote option as well; right now I just get driver=remote and if you pass it directly to make() it won't work without setting those two as well.

@cjcliffe cjcliffe changed the title Remote device should probably return remote:driver= and remote= to match the incoming parameters. Remote device should probably return remote:driver= and remote= to work with make Oct 5, 2015
@guruofquality
Copy link
Contributor

Ahh, good point. To be consistent, SoapyRemote's discovery function should be preserving those keys.

@guruofquality
Copy link
Contributor

Should work now

@cjcliffe
Copy link
Contributor Author

cjcliffe commented Oct 6, 2015

Excellent, tested and working here on Raspberry Pi + RTLSDR & OSX

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

2 participants