From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 86320] Monitor on DisplayPort doesn't wake up Date: Mon, 19 Oct 2015 08:26:33 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0910240259==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 765EA6E59B for ; Mon, 19 Oct 2015 01:26:33 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0910240259== Content-Type: multipart/alternative; boundary="1445243193.0cCA423.25654"; charset="UTF-8" --1445243193.0cCA423.25654 Date: Mon, 19 Oct 2015 08:26:33 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=86320 --- Comment #14 from Morten Leikvoll --- I should warn that some displays does not seem to follow the displayport standard properly. I would recommend trying a different one, and if its related to some models, discuss what to do. I dont have an answer for that. I am working on a embedded displayport source here and find a Dell U2913 2560x1080 monitor (It has a STDP9320-BB "Athena" displayport sink, with unknown firmware) does not report a correct SINK_STATUS (DPCD register 0x00205, bit 0) wich the specification says it should do. Also its seem to lock the LINK_STATUS_UPDATED bit to 1 (in DPCD register 0x00204) But even if this is wrong, it still shows an image. Googling my symptom made me find this thread. Wether to skip this test is a good idea is up for discussion. For an home/office environment, its probably ok, but for an industrial environment it may not be ok. -- You are receiving this mail because: You are the assignee for the bug. --1445243193.0cCA423.25654 Date: Mon, 19 Oct 2015 08:26:33 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 14 on bug 86320 from 
I should warn that some displays does not seem to follow the displayport
standard properly. I would recommend trying a different one, and if its related
to some models, discuss what to do. I dont have an answer for that.

I am working on a embedded displayport source here and find a Dell U2913
2560x1080 monitor (It has a STDP9320-BB "Athena" displayport sink, with unknown
firmware) does not report a correct SINK_STATUS (DPCD register 0x00205, bit 0)
wich the specification says it should do. Also its seem to lock the
LINK_STATUS_UPDATED bit to 1 (in DPCD register 0x00204) But even if this is
wrong, it still shows an image. Googling my symptom made me find this thread.

Wether to skip this test is a good idea is up for discussion. For an
home/office environment, its probably ok, but for an industrial environment it
may not be ok.

You are receiving this mail because:
  • You are the assignee for the bug.
--1445243193.0cCA423.25654-- --===============0910240259== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0910240259==--