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

State explicitly whether this needs UVC or V4L backend for librealsense. #16

Closed
peci1 opened this issue Mar 21, 2016 · 4 comments
Closed

Comments

@peci1
Copy link
Contributor

peci1 commented Mar 21, 2016

I think the readme should contain this kind of information in the install section.

@mkhansenbot
Copy link

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.

@peci1
Copy link
Contributor Author

peci1 commented Apr 11, 2016

What about explicitly stating it works with both? :)

@mkhansenbot mkhansenbot reopened this Apr 12, 2016
@mkhansenbot
Copy link

OK, we're going to update the BKC in a future release to show that we're testing with the V4L backend.

@mkhansenbot
Copy link

This is now part of our BKC. I'm closing this issue.

icarpis pushed a commit to icarpis/realsense that referenced this issue Sep 17, 2017
130s added a commit to 130s/realsense that referenced this issue Feb 16, 2019
…_cherry_upstream

Added code to fix hardware reset issues
@comwise comwise mentioned this issue Oct 12, 2019
YoshuaNava added a commit to YoshuaNava/realsense that referenced this issue Jun 30, 2020
…_upstream_2.2.3

Feature/sync upstream 2.2.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants