From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Marco Chiappero <marco@absence.it>
Cc: platform-driver-x86@vger.kernel.org,
Javier Achirica <achirica@gmail.com>,
Mattia Dongili <malattia@linux.it>
Subject: Re: Commit 7751ab8e600f26e10c2ba12a92d48a4852a51da8
Date: Tue, 12 Apr 2011 16:20:09 +0100 [thread overview]
Message-ID: <20110412152009.GA32032@srcf.ucam.org> (raw)
In-Reply-To: <4D9B4094.4010609@absence.it>
On Tue, Apr 05, 2011 at 06:17:24PM +0200, Marco Chiappero wrote:
> I just wanted to report possible issues related to the new backlight
> control implemented in commit
> 7751ab8e600f26e10c2ba12a92d48a4852a51da8 [sony-laptop: implement new
> backlight control method]. I and Javier Achirica have been using it
> for a while on different notebook models and agree that values close
> to 0 are far too dark to be useful, while 0 means totally off for
> both. Moreover flickering has been reported with CCFL LCDs (still
> present on a few models, such as the Vaio F) by another tester.
> In fact, with these Vaios, Windows never goes below a certain model
> specific backlight lower bound, provided along with the ALS
> capability. However, this requires further code not yet implemented
> (or the ALS support already available but not yet included). Please
> consider correcting or delaying that patch.
Hmm. How low is useful? There's no real problem with shifting everything
by an offset.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-04-12 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 16:17 Commit 7751ab8e600f26e10c2ba12a92d48a4852a51da8 Marco Chiappero
2011-04-12 15:20 ` Matthew Garrett [this message]
2011-04-13 16:50 ` Marco Chiappero
2011-04-13 16:53 ` Matthew Garrett
2011-04-14 7:37 ` Marco Chiappero
2011-04-14 22:42 ` Mattia Dongili
2011-04-16 13:04 ` [PATCH] sony-laptop: limit brightness range to DSDT provided ones Mattia Dongili
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=20110412152009.GA32032@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=achirica@gmail.com \
--cc=malattia@linux.it \
--cc=marco@absence.it \
--cc=platform-driver-x86@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