From mboxrd@z Thu Jan  1 00:00:00 1970
From: Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [pull] drm-intel-fixes
Date: Wed, 22 May 2013 09:13:06 +0200
Message-ID: <CAKMK7uGtX4krdUWXA+VGpXASL7g+sFUhM=7D-bO+MzP_gc22jQ@mail.gmail.com>
References: <20120910072817.GB5387@phenom.ffwll.local>
	<CACP_E+KgsxDcHNifSv08D=1zbMpDuW4JDdtxhavba=TvFJe8hA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
In-Reply-To: <CACP_E+KgsxDcHNifSv08D=1zbMpDuW4JDdtxhavba=TvFJe8hA@mail.gmail.com>
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: =?ISO-8859-1?Q?St=E9phane_Marchesin?= <stephane.marchesin@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>, DRI Development <dri-devel@lists.freedesktop.org>
List-Id: dri-devel@lists.freedesktop.org

On Wed, May 22, 2013 at 3:24 AM, St=E9phane Marchesin
<stephane.marchesin@gmail.com> wrote:
> On Mon, Sep 10, 2012 at 12:28 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
>> Hi Dave,
>>
>> You're pull just reminded me that I've been sitting on a few small -fixe=
s,
>> too. Nothing really major at all:
>> - fixup edp setup sequence (Dave)
>> - disable sdvo hotplug for real, this is a fixup for a messed-up
>>   regression fixer (Jani)
>> - don't expose dysfunctional backlight driver (Jani)
>
> Hi Daniel,
>
> This change ("don't expose dysfunctional backlight driver") regresses
> the backlight on Chromebooks, where we don't run the vbios.

Presuming the patch works as advertised it only stops publishing an
intel backlight driver which won't work. How does that break stuff?

Or do you somehow update the max blc stuff only once i915.ko is loaded?

I'm decently confused how that one blows up ...

Yours, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch