public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom St Denis <tstdenis@elliptictech.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: linux-kernel@vger.kernel.org,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Brightness control fails between 3.6.8 and 3.7.0-rc7 (Intel 915/Dell Vostro 3560)
Date: Sun, 2 Dec 2012 08:49:33 -0500 (EST)	[thread overview]
Message-ID: <1738269086.121732.1354456173261.JavaMail.root@elliptictech.com> (raw)
In-Reply-To: <CAKMK7uGrLvmDa+pqStAK_E_rEmgAgR+BO6+-m2dgUk6Ut6DuCQ@mail.gmail.com>

Ok so on v3.7-rc1 [and I suspect up] I can manually control the brightness by echoing to 

/sys/class/backlight/intel_backlight/brightness

But I still can't use the buttons to control it (it only goes one tick down from max and stops there).  I'm using GNOME3 from a x86_64 unstable debian install [up to date with latest].

I just noticed that under v3.7 I have a new directory /sys/class/backlight/acpi_video1 which is what GNOME is actually controlling.  I can't disable ACPI video control so is there a workaround?

Tom



----- Original Message -----
> From: "Daniel Vetter" <daniel.vetter@ffwll.ch>
> To: "Tom St Denis" <tstdenis@elliptictech.com>
> Cc: linux-kernel@vger.kernel.org, "intel-gfx" <intel-gfx@lists.freedesktop.org>, "dri-devel"
> <dri-devel@lists.freedesktop.org>
> Sent: Sunday, 2 December, 2012 6:43:14 AM
> Subject: Re: Brightness control fails between 3.6.8 and 3.7.0-rc7 (Intel 915/Dell Vostro 3560)
> 
> Including a bunch more lists to the cc.
> 
> On Sun, Dec 2, 2012 at 12:42 PM, Daniel Vetter
> <daniel.vetter@ffwll.ch> wrote:
> > On Sun, Dec 2, 2012 at 12:32 PM, Tom St Denis
> > <tstdenis@elliptictech.com> wrote:
> >> I've narrowed it down to sometime between v3.6.8 and v3.7-rc1.  So
> >> none of the v3.7 series will work with this GPU/panel.
> >
> > Hm, that's still a few hundred relevant commits intermingled with a
> > few thousand that likely don't matter ;-) Can you please attempt a
> > kernel bisect with git? For a nice howto check out
> > http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to-find-buggy-kernel-patches/
> >
> > Also, can you please check which of the different backlight
> > controls
> > in /sys/class/backlight work on 3.6 (and whether any of them still
> > work on 3.7)?
> >
> > Thanks, Daniel
> > --
> > Daniel Vetter
> > Software Engineer, Intel Corporation
> > +41 (0) 79 365 57 48 - http://blog.ffwll.ch
> 
> 
> 
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
> 

  reply	other threads:[~2012-12-02 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <268628838.121506.1354405604521.JavaMail.root@elliptictech.com>
2012-12-01 23:49 ` Brightness control fails between 3.6.8 and 3.7.0-rc7 (Intel 915/Dell Vostro 3560) Tom St Denis
2012-12-02 11:32   ` Tom St Denis
2012-12-02 11:42     ` Daniel Vetter
2012-12-02 11:43       ` Daniel Vetter
2012-12-02 13:49         ` Tom St Denis [this message]
2012-12-02 14:42           ` Daniel Vetter
2012-12-02 15:33             ` Tom St Denis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1738269086.121732.1354456173261.JavaMail.root@elliptictech.com \
    --to=tstdenis@elliptictech.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox