Updated https://github.com/rhabbachi/displaylink-pkgbuild with @PlusMinus suggestions.
Search Criteria
Package Details: displaylink 6.0-0
Package Actions
| Git Clone URL: | https://aur.archlinux.org/displaylink.git (read-only, click to copy) |
|---|---|
| Package Base: | displaylink |
| Description: | Linux driver for DisplayLink devices |
| Upstream URL: | https://www.synaptics.com/products/displaylink-graphics |
| Keywords: | dock gpu graphics usb |
| Licenses: | GPL2, custom, LGPL2.1 |
| Submitter: | Hideaki |
| Maintainer: | endorfina |
| Last Packager: | endorfina |
| Votes: | 104 |
| Popularity: | 2.73 |
| First Submitted: | 2015-08-04 23:24 (UTC) |
| Last Updated: | 2024-05-06 08:33 (UTC) |
Dependencies (5)
- evdiAUR (evdi-amd-vmap-textureAUR, evdi-compat-gitAUR, evdi-gitAUR)
- libusb (libusb-gitAUR)
- gawk (gawk-gitAUR, busybox-coreutilsAUR) (make)
- grep (grep-gitAUR, busybox-coreutilsAUR, grep-compatAUR) (make)
- wget (wget-gitAUR, wurlAUR) (make)
Required by (1)
Sources (7)
rhabbachi commented on 2016-09-15 14:22 (UTC)
rhabbachi commented on 2016-09-15 14:17 (UTC)
The thing is AFAIK This module is not functional using the latest 4.7 kernel that is the current kernel in Arch.
rhabbachi commented on 2016-09-15 14:14 (UTC) (edited on 2016-09-15 14:15 (UTC) by rhabbachi)
> Maybe it makes more sense to put evdi into another package.
In a more generic case I would 100% agree. But for this package I'm not really sure. Will the eventual evdi package be installed without this package? And what will this package (displaylink) depend on? should all the evdi packages `provides= "evdi"`?
I think to mitigate the confusion that might arise we can keep this package using the default evdi module provided by the displaylink site and create another package (displaylink-latest-evdi or something similar) that uses the latest evdi module.
PlusMinus commented on 2016-09-15 13:41 (UTC)
Maybe it makes more sense to put evdi into another package.
PlusMinus commented on 2016-09-15 13:21 (UTC)
Thanks for the effort @rhabbachi I added some inline comments on your git.
rhabbachi commented on 2016-09-15 13:04 (UTC)
updated the PKGBUILD to use the latest evdi module from https://github.com/DisplayLink/evdi. Feedback welcome https://github.com/rhabbachi/displaylink-pkgbuild
marco44 commented on 2016-08-24 12:59 (UTC)
The 1.68 displayed on the website seems to have the same checksum as the 1.62 (the .run file included).
There are available patches to make evdi compile in 4.7 (on github)
RubenKelevra commented on 2016-08-22 16:14 (UTC)
please add this patch:
https://github.com/RobertCochran/evdi/commit/0d80a3b7a8017709449a9938d14a5d10caadf389.patch
RubenKelevra commented on 2016-08-22 16:12 (UTC)
/evdi/1.1.62/build/.tmp_evdi_main.o /var/lib/dkms/evdi/1.1.62/build/evdi_main.c
/var/lib/dkms/evdi/1.1.62/build/evdi_main.c: In Funktion »evdi_driver_unload«:
/var/lib/dkms/evdi/1.1.62/build/evdi_main.c:82:2: Fehler: Implizite Deklaration der Funktion »drm_connector_unplug_all« [-Werror=implicit-function-declaration]
drm_connector_unplug_all(dev);
^~~~~~~~~~~~~~~~~~~~~~~~
cc1: Einige Warnungen werden als Fehler behandelt
make[2]: *** [scripts/Makefile.build:290: /var/lib/dkms/evdi/1.1.62/build/evdi_main.o] Fehler 1
make[1]: *** [Makefile:1461: _module_/var/lib/dkms/evdi/1.1.62/build] Fehler 2
yah00ka commented on 2016-08-15 09:18 (UTC)
installation fails since kernel got upgraded to 4.7.0
A fix can be found here : https://github.com/DisplayLink/evdi/issues/32
Pinned Comments