From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Scot Doyle <lkml14@scotdoyle.com>,
Tim Gardner <tim.gardner@canonical.com>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, Adam Borowski <kilobyte@angband.pl>
Subject: Re: [PATCH linux-next V2] tty: Disable default console blanking interval
Date: Thu, 23 Mar 2017 08:42:03 -0400 [thread overview]
Message-ID: <d7ca4c04-eb47-e0b5-7ee7-e69d96857f4d@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1703222010220.2307@pc>
On 2017-03-22 21:32, Scot Doyle wrote:
> On Wed, 22 Mar 2017, Tim Gardner wrote:
>> BugLink: http://bugs.launchpad.net/bugs/869017
>>
>> Console blanking is not enabling DPMS power saving (thereby negating any
>> power-saving benefit), and is simply turning the screen content blank. This
>> means that any crash output is invisible which is unhelpful on a server
>> (virtual or otherwise).
>>
>> Furthermore, CRT burn in concerns should no longer govern the default case.
>> Affected users could always set consoleblank on the kernel command line.
>
> Does screen blanking save some power by disabling the cursor blink?
>
Unless you're dealing with ancient hardware, the difference in power
usage is probably on the order of single digit micro-watts, which is not
worth worrying about on almost anything you would expect to have a
console display connected to.
next prev parent reply other threads:[~2017-03-23 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 13:50 [PATCH linux-next] tty: Disable default console blanking interval Tim Gardner
2017-03-22 14:14 ` Austin S. Hemmelgarn
2017-03-22 14:54 ` Greg Kroah-Hartman
2017-03-22 15:07 ` [PATCH linux-next V2] " Tim Gardner
2017-03-23 1:32 ` Scot Doyle
2017-03-23 12:42 ` Austin S. Hemmelgarn [this message]
2017-03-24 2:27 ` Scot Doyle
2017-03-23 2:06 ` [PATCH linux-next] " Adam Borowski
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=d7ca4c04-eb47-e0b5-7ee7-e69d96857f4d@gmail.com \
--to=ahferroin7@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml14@scotdoyle.com \
--cc=tim.gardner@canonical.com \
/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