From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Richter Subject: Re: Broken in 3.10.10 Date: Tue, 08 Oct 2013 19:06:19 +0200 Message-ID: <52543B8B.2010604@math.tu-berlin.de> References: <1377298288-2830-1-git-send-email-przanoni@gmail.com> <20130830172552.GN11428@intel.com> <29427_1378101775_52242A0E_29427_747_1_20130902060151.GE9374@phenom.ffwll.local> <524FCEE8.4010307@math.tu-berlin.de> <29761_1380973482_524FFBA9_29761_4042_1_20131005114432.GE9395@intel.com> <52504289.10107@math.tu-berlin.de> <29761_1381001928_52506AC8_29761_5606_1_20131005193904.GX31334@phenom.ffwll.local> <52509C3D.2020603@math.tu-berlin.de> <5132_1381149082_5252A99A_5132_80_1_CAKMK7uHkOJ=urFKCacocf_i+6YL9Azf5vK=Au-kRJMi=sNBP1Q@mail.gmail.com> <52532EA3.90200@math.tu-berlin.de> <26192_1381221546_5253C4A9_26192_7222_1_CAKMK7uGvk9vuNXunutyHjkGjvBWsv7ObN02EfbG2679MtQ5M=A@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from medousa.rus.uni-stuttgart.de (medousa.rus.uni-stuttgart.de [129.69.192.4]) by gabe.freedesktop.org (Postfix) with ESMTP id 5EC1DE6A4E for ; Tue, 8 Oct 2013 10:07:25 -0700 (PDT) In-Reply-To: <26192_1381221546_5253C4A9_26192_7222_1_CAKMK7uGvk9vuNXunutyHjkGjvBWsv7ObN02EfbG2679MtQ5M=A@mail.gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Daniel Vetter Cc: intel-gfx List-Id: intel-gfx@lists.freedesktop.org On 08.10.2013 10:39, Daniel Vetter wrote: > On Tue, Oct 8, 2013 at 9:24 AM, Daniel Vetter wrote: >> I guess step one is to bisect the regression in 3.11. Fixing things on >> top of 3.10 is imo pointless if later kernels break things harder ... > btw the two SNA patches I've just submitted should improve things > quite a bit. If that gets rid of the black screen then there's not > really a need to do the bisect. I'll try to pull these right now. The system is a bit on the slow side, given its age, and it might take the whole evening. Unfortunately, I won't have it available until next weekend, and then for quite a while. BTW, there is not really any sense in trying to re-program the DVO once it is locked up, the "for" loop around it can simply go away. If it is stuck, nothing will made it un-stuck until the DPLL is again correct, and once the DPLL is correct, it works on first attempt. On a second note: The current ns2501 code also assumes that the display is 1024x768, which is probably *often* correct, but not always correct. Thus, it turns of scaling for this resolution, and turns it on for all others, where the scaling parameters come from the bios of the old lifebook I have here. Would be interesting to see whether this specific DVO was used on a system with any other display resolution, and extract the DVO scaling parameters from there. Greetings, Thomas