-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
State explicitly whether this needs UVC or V4L backend for librealsense. #16
Comments
This was discussed internally and we have no code in this ROS package that is specific to V4L or UVC, so we don't believe the readme file should restrict or document a requirement for one or the other. We think this should be part of the librealsense readme which it is. |
What about explicitly stating it works with both? :) |
OK, we're going to update the BKC in a future release to show that we're testing with the V4L backend. |
This is now part of our BKC. I'm closing this issue. |
Update pt node & readme & launch files
…_cherry_upstream Added code to fix hardware reset issues
…_upstream_2.2.3 Feature/sync upstream 2.2.3
I think the readme should contain this kind of information in the install section.
The text was updated successfully, but these errors were encountered: