From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "* SAMÍ *" <miaousami@hotmail.com>
Cc: linux-kernel@vger.kernel.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Aaron Lu <aaron.lu@intel.com>,
Igor Gnatenko <i.gnatenko.brain@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Linux 3.11-rc2 [backlight] [ASUS N56VZ]
Date: Wed, 24 Jul 2013 21:39:38 +0200 [thread overview]
Message-ID: <17420057.BAULu67LQ3@vostro.rjw.lan> (raw)
In-Reply-To: <BLU0-SMTP125E791F01E26C3D60D7353A6680@phx.gbl>
On Wednesday, July 24, 2013 08:43:00 PM * SAMÍ * wrote:
> Hi,
>
> it seems a lot of people are complaining about the backlight pull
> request of RC2.
>
> This is to tell you how it saved my life:
> - Changing brightness from Fn keys does work
> - Writing to /sys/class/backlight/intel_backlight/brightness does work
> - Changing brightness from gnome brightness settings does work
> --> It seems everything is now working (it wasn't before).
> --> I appreciate your patch and I am going to be sad if you revert it :-)
Well, there seems to be a number of people who'll be equally unhappy if I don't
do that. Unfortunately for you, things work for them without that patch.
The source of the problem seems to be that the i915's backlight support doesn't
work for all those people, although it should work anyway in principle. So to
me the way to go seems to be to revert the patch for now, fix the i915
backlight interface for them and try to apply it again when we're more
confident about the i915 backlight.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-07-24 19:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 18:43 * SAMÍ *
[not found] ` <CAFMg4WB21dWV6c+hxzrXR_0pSfnayFPZGx0byX6pKjMS5SDoqQ@mail.gmail.com>
2013-07-24 19:29 ` Rafael J. Wysocki
2013-07-24 19:39 ` Rafael J. Wysocki [this message]
2013-07-24 20:39 ` Linus Torvalds
2013-07-24 21:02 ` [Intel-gfx] " Daniel Vetter
2013-07-24 21:05 ` Linus Torvalds
2013-07-24 21:23 ` Rafael J. Wysocki
2013-07-25 8:09 ` Jani Nikula
2013-07-25 11:58 ` Rafael J. Wysocki
2013-07-25 12:34 ` Jani Nikula
2013-07-25 12:57 ` Rafael J. Wysocki
2013-07-29 19:36 ` * SAMÍ *
2013-07-29 20:03 ` Rafael J. Wysocki
2013-07-29 21:53 ` * SAMÍ *
2013-07-29 22:11 ` Rafael J. Wysocki
2013-07-29 23:38 ` Aaron Lu
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=17420057.BAULu67LQ3@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=aaron.lu@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=i.gnatenko.brain@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaousami@hotmail.com \
--cc=mjg59@srcf.ucam.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®