summarylogtreecommitdiffstats
path: root/release-note.txt
diff options
context:
space:
mode:
authorPusMinus02017-08-17 14:13:22 +0200
committerPusMinus02017-08-17 14:13:22 +0200
commit19e33e729ae045b46b906ab760167781cf80c504 (patch)
tree82b8b85bf4d75621c1261158560739afffba30fa /release-note.txt
parentc993765f9b34cdc3187554ec4f1ee65f105f4b75 (diff)
downloadaur-19e33e729ae045b46b906ab760167781cf80c504.tar.gz
update pkg
Diffstat (limited to 'release-note.txt')
-rw-r--r--release-note.txt37
1 files changed, 9 insertions, 28 deletions
diff --git a/release-note.txt b/release-note.txt
index c1bbc99b8ca9..8fdc031a8373 100644
--- a/release-note.txt
+++ b/release-note.txt
@@ -3,12 +3,12 @@
DisplayLink Ubuntu Software Release Note
-Version: 1.3.52
-Date: 15th February 2017
+Version: 1.3.54
+Date: 14th June 2017
DisplayLink DL-5xxx, DL-41xx, DL-3x00 Firmware Version: 9.1.53.82735
DisplayLink DL-6xxx Firmware Version: 9.1.53.82737
-Extensible Virtual Display Interface version included: 1.3.43
+Extensible Virtual Display Interface version included: 1.4.1
=============================================================================
=============================================================================
@@ -17,7 +17,7 @@ Extensible Virtual Display Interface version included: 1.3.43
A. Introduction
===============
-This is DisplayLink Driver Software v1.3 for Ubuntu. It provides production quality support for DisplayLink USB 3.0 devices on specific variants of desktop Ubuntu Linux.
+This is DisplayLink Driver Software v1.3.1 for Ubuntu. It provides production quality support for DisplayLink USB 3.0 devices on specific variants of desktop Ubuntu Linux.
The driver enables video support for products using DisplayLink USB 3.0 technology. Standard native Ubuntu drivers provide support for DisplayLink audio and Ethernet interfaces.
@@ -35,8 +35,7 @@ B. Contents
A. Introduction
A1. Important notes about DL-6xxx, DL-5xxx, DL-3xxx and DL-41xx Firmware
B. Contents
-C. New features
-C1. Issues fixed
+C. Issues fixed
D. Supported O/S variants
E. Release components
F. How to Install
@@ -44,31 +43,13 @@ G. Supported Features & Hardware
H. Limitations & Known issues
I. Future Development
-C. New features
+C. Issues fixed
===============
-DisplayLink Driver Software v1.3 for Ubuntu delivers support for DL-6xxx generation devices.
-C1. Issues fixed
-===============
-
-Issues fixed since DisplayLink Driver Software v1.2.1 for Ubuntu (1.2.65)
+Issues fixed since DisplayLink Driver Software v1.3.0 for Ubuntu (1.3.52)
-----------------------------------------------------------------------
-Mixed content while switching between Firefox tabs on DisplayLink screen. (22540)
-
-Blank DisplayLink screen after machine restart if OS kernel was upgraded. (23735)
-
-Leftovers on DisplayLink screen when using Gnome 2 (Metacity). (23970)
-
-Blank DisplayLink screen at 1366x768 resolution. (24082)
-
-Leftovers on DisplayLink screen when using KDE. (24113)
-
-Low performance on 4kp60 resolution (24379).
-
-In a multimonitor setup, disconnecting one DisplayLink screen may cause freeze of the remaining screen. (24207)
-
-After embedded firmware update one of the chained devices may not be visible in the system. (24514)
+DisplayLink EVDI module is not compatible with Linux Kernel 4.12.
D. Supported O/S variants
=========================
@@ -127,4 +108,4 @@ DisplayLink are open to suggestions and feedback on improving the proposed archi
- The communication between the EVDI kernel module and the wrapper libevdi library is not access-controlled or authenticated. This could be improved in future releases, making it harder to compromise the data EVDI is sending and receiving.
-- EVDI kernel module driver is currently a platform_driver, for multiple reasons; most importantly because virtual displays are not discoverable, i.e. cannot be enumerated at the hardware level. EVDI is also a generic device, not tied to any particular kind of device, transport layer or a bus. \ No newline at end of file
+- EVDI kernel module driver is currently a platform_driver, for multiple reasons; most importantly because virtual displays are not discoverable, i.e. cannot be enumerated at the hardware level. EVDI is also a generic device, not tied to any particular kind of device, transport layer or a bus.