From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 81382] Text console blanking does not go away
Date: Thu, 11 Sep 2014 10:42:35 +0000 [thread overview]
Message-ID: <bug-81382-502-M003rErWle@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-81382-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 854 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=81382
--- Comment #9 from Denys Vlasenko <vda.linux@googlemail.com> ---
(In reply to comment #7)
> Ok, this fix work, but cause another problem (tested with 3.15.5+patch and
> 3.16.1).
>
> When display goes off, backlight goes off.
> When display goes on, backlight is set to MAX.
> When display goes off again, backligh remains MAX.
> After pressing key, LCD works, backlight stay at MAX level.
> When display goes off, backlight is still MAX.
I would say it means that merely treating backlight value of 0 as MAX is not
the best idea.
Maybe we need an additional bool variable "failed to read initial BL value,
don't ever try to set it", set it if initial read of BL value is 0, and if it
is set, never try to change BL level?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1713 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-09-11 10:42 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 11:25 [Bug 81382] New: Text console blanking does not go away bugzilla-daemon
2014-07-15 12:29 ` [Bug 81382] " bugzilla-daemon
2014-07-15 13:37 ` bugzilla-daemon
2014-07-15 13:55 ` bugzilla-daemon
2014-07-15 14:24 ` bugzilla-daemon
2014-07-15 14:33 ` bugzilla-daemon
2014-07-16 18:26 ` bugzilla-daemon
2014-09-05 20:58 ` bugzilla-daemon
2014-09-10 20:34 ` bugzilla-daemon
2014-09-11 10:42 ` bugzilla-daemon [this message]
2014-09-11 13:58 ` bugzilla-daemon
2014-09-12 22:40 ` bugzilla-daemon
2014-09-13 20:43 ` bugzilla-daemon
2014-09-15 20:41 ` bugzilla-daemon
2014-09-15 20:47 ` bugzilla-daemon
2014-09-16 7:00 ` bugzilla-daemon
2014-09-16 7:01 ` bugzilla-daemon
2014-09-16 7:02 ` bugzilla-daemon
2014-09-16 7:17 ` bugzilla-daemon
2014-09-17 1:00 ` bugzilla-daemon
2014-09-17 1:04 ` bugzilla-daemon
2014-09-17 7:07 ` bugzilla-daemon
2014-09-17 15:38 ` bugzilla-daemon
2014-09-17 15:39 ` bugzilla-daemon
2014-09-17 16:42 ` bugzilla-daemon
2014-09-18 7:54 ` bugzilla-daemon
2014-09-18 13:09 ` bugzilla-daemon
2014-09-18 13:10 ` bugzilla-daemon
2014-09-18 19:27 ` bugzilla-daemon
2014-09-18 19:28 ` bugzilla-daemon
2014-09-19 13:14 ` bugzilla-daemon
2014-09-19 15:38 ` bugzilla-daemon
2014-09-19 15:40 ` bugzilla-daemon
2014-09-19 16:20 ` bugzilla-daemon
2014-09-27 21:36 ` bugzilla-daemon
2014-09-28 0:40 ` bugzilla-daemon
2015-04-21 20:05 ` bugzilla-daemon
2015-04-21 20:11 ` bugzilla-daemon
2015-04-21 20:27 ` bugzilla-daemon
2015-04-22 9:32 ` bugzilla-daemon
2015-04-23 6:02 ` bugzilla-daemon
2015-04-23 14:12 ` bugzilla-daemon
2015-04-23 14:15 ` bugzilla-daemon
2015-04-24 13:59 ` bugzilla-daemon
2016-08-13 12:01 ` bugzilla-daemon
2016-08-15 13:40 ` bugzilla-daemon
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=bug-81382-502-M003rErWle@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.