-
Notifications
You must be signed in to change notification settings - Fork 4.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
Question: how to confirm that the kernel module is patched correctly? #6837
Comments
@jurc192 , there are two things to review - formats and metadata.
In case you want to better understand which formats were singled out you can use Imo the quickest indirect way of verifying the kernel patches is checking the presence of metadata attributes. Specifically for LTS 5.4 - currently it has no DKMS but you can do it with installation script from installation guide
|
Thanks! |
Sorry to jump on an old thread, but does a command line tool exist on a headless (non X11, no window manager) to check the presence of metadata attributes? ie.e can you see these without using realsense-viewer? Basically trying to confirm that this unit indeed has the v4l backend with kernel patches, and not the RSUSB, and it does not have realsense-viewer. I can confirm only the dmesg warning about the 36315752-1a66-a242-9065-d01814a8ef8a video format is showing (no others), but want to make sure 100%. |
Issue Description
Short question: how can we check that patched kernel module is patched correctly?
I am trying to compare the performance between RSUSB and kernel modules, compiling the realsense SDK from source on Linux. Since officially the 5.4 kernel is not being supported yet, I want to try patching it manually. Is there a simple way to verify that everything is fine, that the kernel module is patched correctly and being used by realsense? Is this all about the uvcvideo driver/module or are there other files/modules that need patching?
Is this related to: "uvcvideo: Unknown video format 36315752-1a66-a242-9065-d01814a8ef8a" error messages?
The text was updated successfully, but these errors were encountered: