Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759707AbdCVNvA (ORCPT ); Wed, 22 Mar 2017 09:51:00 -0400 Received: from mail-io0-f171.google.com ([209.85.223.171]:35824 "EHLO mail-io0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758734AbdCVNuw (ORCPT ); Wed, 22 Mar 2017 09:50:52 -0400 From: Tim Gardner To: linux-kernel@vger.kernel.org Cc: Tim Gardner , Greg Kroah-Hartman , Jiri Slaby , Adam Borowski , Scot Doyle Subject: [PATCH linux-next] tty: Disable default console blanking interval Date: Wed, 22 Mar 2017 07:50:32 -0600 Message-Id: <1490190632-10464-1-git-send-email-tim.gardner@canonical.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 981 Lines: 31 BugLink: http://bugs.launchpad.net/bugs/869017 Signed-off-by: Tim Gardner Cc: Greg Kroah-Hartman Cc: Jiri Slaby Cc: Adam Borowski Cc: Scot Doyle --- I'm not particularly knowledgable about console issues. Is a blaknking interval relevant in a post CRT world ? The argument in the bug description seems compelling. drivers/tty/vt/vt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c index 5c4933b..9c99452 100644 --- a/drivers/tty/vt/vt.c +++ b/drivers/tty/vt/vt.c @@ -181,7 +181,7 @@ int console_blanked; static int vesa_blank_mode; /* 0:none 1:suspendV 2:suspendH 3:powerdown */ static int vesa_off_interval; -static int blankinterval = 10*60; +static int blankinterval; core_param(consoleblank, blankinterval, int, 0444); static DECLARE_WORK(console_work, console_callback); -- 2.7.4