Slash Boxes

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 14 submissions in the queue.
posted by martyb on Wednesday April 05 2017, @11:33AM   Printer-friendly
from the coding-skills-on-display dept.

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.
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: 4, Funny) by turgid on Wednesday April 05 2017, @06:12PM (2 children)

    by turgid (4318) on Wednesday April 05 2017, @06:12PM (#489254) Journal

    Is there a problem to be solved? Do you understand the problem?

    Have you examined the existing system sufficiently to understand how it behaves, how it should behave, the difference between its current behaviour and the new desired behaviour and any other parts of the system that depend on the existing behaviour being preserved? If so, what are you going to do about it?

    Can you design a solution? OK, can you design several different solutions so that you can talk about them, appraise them and pick the best one (choose your definition of best carefully).

    Can you implement your chosen solution? Did you have to fix any existing problems first? Did you report them? Did you analyse them enough to understand them thoroughly? Have you inadvertently changed any behaviour that something else depended on? Have you made it difficult to modify other parts of the system?

    You implemented your chosen solution, great. Does it work? Can you prove it? Is it repeatable? Can other people understand the code and any changed existing code? Has someone else reviewed it and pointed out the mistakes you didn't find yourself?

    Did you fix those mistakes and prove that things still work, or work better, and that you didn't accidentally break anything?

    Did anyone who reviewed it come up with any insight into better designs or better solutions? Are they worth implementing?

    Does the system as a whole behave as expected? Would the customer buy it?

    Are you happy for your work to be published for the global peanut gallery to criticise...?

    Some people choose to do this for fun. Others do it hoping to get paid.

    Starting Score:    1  point
    Moderation   +2  
       Interesting=1, Funny=1, Total=2
    Extra 'Funny' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 1, Informative) by Anonymous Coward on Wednesday April 05 2017, @07:09PM (1 child)

    by Anonymous Coward on Wednesday April 05 2017, @07:09PM (#489291)

    You seem to like questions.