From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Richter <thor@math.tu-berlin.de>
Subject: Re: More questions and patches for 835GM/ns2501 DVO
Date: Fri, 15 Nov 2013 19:59:30 +0100
Message-ID: <52866F12.6030006@math.tu-berlin.de>
References: <52768009.7070905@math.tu-berlin.de>
	<20131103171208.GA4167@phenom.ffwll.local>
	<19544_1383498802_52768431_19544_2610_1_20131103171348.GB4167@phenom.ffwll.local>
	<52769D39.5070501@math.tu-berlin.de>
	<20131103211814.GC4167@phenom.ffwll.local>
	<20131106103405.GH14082@phenom.ffwll.local>
	<10422_1384536748_52865AAC_10422_4782_1_20131115173300.GZ22741@phenom.ffwll.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from hydra.rus.uni-stuttgart.de (hydra.rus.uni-stuttgart.de
	[129.69.192.3])
	by gabe.freedesktop.org (Postfix) with ESMTP id 9C970105AA3
	for <intel-gfx@lists.freedesktop.org>;
	Fri, 15 Nov 2013 11:00:25 -0800 (PST)
In-Reply-To: <10422_1384536748_52865AAC_10422_4782_1_20131115173300.GZ22741@phenom.ffwll.local>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=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 <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
List-Id: intel-gfx@lists.freedesktop.org

On 15.11.2013 18:33, Daniel Vetter wrote:

>> To clarify: Do you need this patch to make the single-pipe mode work
>> reliably? It's a bit unclear in your answer ...
>
> To clarify my clarification question: Do you need the above quoted patch
> to make the cursor work better on your system?

Well, at least it avoided one kernel warning. Or rather, I haven't seen 
it since. But otherwise, the cursor works fine. I don't have any 
problems with the cursor whatsoever, it always appears.

> This is not about a WARN or
> the flicker or dual pipe (last time I've asked you kinda went on a
> tangent). I'm asking again since this patch for the cursor code is
> currently blocked from merging because I couldn't get a clear "this is
> needed, yes" from you.

It's hard to say whether it is needed, unfortunately. The kernel warning 
is not so easy to provoke, and there is no clear way to reproduce it. 
All I can say is that I haven't seen it since, and the patch has surely 
not made anything worse, so I would say go for it and include it.

Greetings,
	Thomas