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

Question: how to check if you are using RSUSB or a patched kernel module #6836

Closed
jurc192 opened this issue Jul 15, 2020 · 3 comments
Closed

Comments

@jurc192
Copy link

jurc192 commented Jul 15, 2020

Required Info
Camera Model D4000
Firmware Version 05.12.06.00
Operating System & Version Linux
Kernel Version (Linux Only) (5.4.0)
Platform PC
SDK Version 2.36.0
Language python
Segment others }

Issue Description

Short question: how can we verify if RealSense SDK is using RSUSB or (patched) kernel drivers?

I am trying to compare the performance between the two, compiling the realsense SDK from source on Linux.
Is there a reliable way (sanity-check) to see which of the two is currently being used- rsusb or kernel drivers?

@jurc192 jurc192 changed the title Question: how to confirm that you are using RSUSB or a patched kernel module Question: how to check if you are using RSUSB or a patched kernel module Jul 15, 2020
@dorodnic
Copy link
Contributor

Hi @jurc192
We've been planning dedicated API for this for a while, but for now you can look at Physical Port camera info. For V4L2 it would be something...v4l2... while for RSUSB it would be 1-2-3.
With V4L2, you can check if its patched by checking timestamp domain property of a frame.

@RealSenseSupport
Copy link
Collaborator

Hi @jurc192 Do you need further help on this? If we don't hear from you in 7 days, this issue will be closed.

@jurc192
Copy link
Author

jurc192 commented Jul 20, 2020

Thanks for your answer!
I can indeed see the difference by checking RealSense Viewer app -> info -> Physical port :)

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