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

Issue with Kernel 4.4.103-36 and DKMS 2.2.1.0 #110

Open
jessecooper opened this Issue Dec 19, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@jessecooper
Copy link

jessecooper commented Dec 19, 2017

Followed the advice of this comment to get the module to compile in the displaylink-install. Here is a diff:

--- ../evdi_fb.c        2017-10-06 05:58:54.000000000 -0500
+++ evdi_fb.c   2017-12-18 14:36:25.458211744 -0600
@@ -229,7 +229,7 @@
                ret =
                    dma_buf_begin_cpu_access(
                        ufb->obj->base.import_attach->dmabuf,
-#if KERNEL_VERSION(4, 6, 0) > LINUX_VERSION_CODE
+#if KERNEL_VERSION(4, 6, 0) < LINUX_VERSION_CODE
                        0, ufb->obj->base.size,
 #endif
                        DMA_FROM_DEVICE);
@@ -247,7 +247,7 @@
 
        if (ufb->obj->base.import_attach)
                dma_buf_end_cpu_access(ufb->obj->base.import_attach->dmabuf,
-#if KERNEL_VERSION(4, 6, 0) > LINUX_VERSION_CODE
+#if KERNEL_VERSION(4, 6, 0) < LINUX_VERSION_CODE
                                       0, ufb->obj->base.size,
 #endif

Hopefully this will help if anyone else runs into the same issue. A better solution might be to just change the KERNEL_VERSION(4, 6, 0) to KERNEL_VERSION(4, 4, 0).

@xmentos

This comment has been minimized.

Copy link

xmentos commented Jan 8, 2018

Because of recent LTS kernel patches I think it would be more correct to change the macros to the following:

#if KERNEL_VERSION(4, 4, 102) > LINUX_VERSION_CODE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment