Stories
Slash Boxes
Comments

SoylentNews is people

Linux, Meet DisplayPort

posted by martyb on Wednesday April 05 2017, @11:33AM   Printer-friendly
from the coding-skills-on-display dept.

CoolHand writes:

LinuxGizmos has an interesting article on how an Intel Engineer fixed up Linux's DisplayPort compliance, and got the kernel patch moved upstream.

At ELC 2017, Intel's Manasi Navare described how she patched Linux 4.12 for true DisplayPort compliance, and offered tips on pushing patches upstream.

If you've ever hooked up a Linux computer to a DisplayPort monitor and encountered only a flickering or blank screen, we've got good news for you. A graphics kernel developer at Intel's Open Source Technology Center has solved the problem with a patch that will go into Linux Kernel 4.12. Manasi Navare's patch modifies Atomic Kernel Mode Setting (KMS) technology to gracefully drop down to a lower resolution to display the image.

"Someone had to fix this problem, so I said okay, I have the knowledge and I have the community to help me," said Navare at the recent Embedded Linux Conference.

Original Submission

 
This discussion has been archived. No new comments can be posted.
Linux, Meet DisplayPort | Log In/Create an Account | Top | 27 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by JoeMerchant on Wednesday April 05 2017, @01:45PM (2 children)

    by JoeMerchant (3937) on Wednesday April 05 2017, @01:45PM (#489139)

    I have a 4K HDMI monitor connected to a Broadwell NUC running Windows 10, and it still can't get itself right most of the time.

    Watch a 2 hour movie on Netflix, at some point there will be at least 30 seconds of blank screen while the monitor and CPU are re-syncing with each other. MTBF on the HDMI sound interface seems to be around 12 hours, sometimes faster, sometimes slower, but eventually if you run it long enough, the sound will go away.

    It's down to drivers, I'm sure - but even Windows 10 doesn't seem to be getting their HDMI drivers completely right. I know 4K is "challenging" - but, please, we've been doing HDMI for over a decade, can we get it right already?

    --
    🌻🌻 [google.com]
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 2) by Scruffy Beard 2 on Wednesday April 05 2017, @04:08PM (1 child)

    by Scruffy Beard 2 (6030) on Wednesday April 05 2017, @04:08PM (#489188)

    That is probably the DRM fucking you over. (You using The Edge browser to get 4K instead of 720P?)

    • (Score: 2) by JoeMerchant on Wednesday April 05 2017, @04:17PM

      by JoeMerchant (3937) on Wednesday April 05 2017, @04:17PM (#489194)

      Chrome, and from across the room I don't really care if it's 4K or 720p.

      Yeah, those could be DRM glitches on Netflix. When playing .mkv files back on Kodi, we get different glitches :(

      --
      🌻🌻 [google.com]