View Single Post
Old 08-29-2018, 03:18 PM   #503
paultzirides
Member
 
Join Date: Jun 2013
Posts: 50
Default

Quote:
Originally Posted by gabhain View Post
That implies that they have a working system extension, which they dont. A beta driver on a beta OS that runs on some hardware doesnt really count after like 8 months. The article discusses whitelisting system extensions using Jamf, if it was a whitelisting issue then users would have a prompt to manually add the extension. Non enterprise users wouldnt have Jamf most likely. Ive had to whitelist extensions in jamf before, it would be awesome if that was the issue as its easily fixed but unfortunately its not

OWC, Caldigit and HP had this working on their docks with zero downtime for users so this is a Displaylink issue not an Apple one.
Unfortunately, you're a little off on your assessment of OWC, Caldigit, and HP docks. Those all use Thunderbolt 3, not USB-C, despite the cable looking identical to USB-C. Those docks use either the "alt-mode" function of USB-C (which passes video data over the DisplayPort channel), or native Thunderbolt 3. Each of those are seen by the OS as a native display, and the other functions of those docks have work in a similar manner. That functionality is dictated by the hardware itself. DisplayLink does not use DisplayPort or Thunderbolt, it's a different set of hardware that pipes a number of disparate hardware functions over USB, and requires special drivers to be able to do that.

Thunderbolt docks are expensive to produce and are expensive to purchase. DisplayLink is a lower-cost alternative that most people find appealing because of that lower cost. Hopefully Apple is able to work with the DL team to help them get to where they need to go with this driver.

Last edited by paultzirides; 08-29-2018 at 03:19 PM. Reason: Clarity
paultzirides is offline   Reply With Quote