[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150328003503.GB27135@vapier>
Date: Fri, 27 Mar 2015 20:35:03 -0400
From: Mike Frysinger <vapier@...too.org>
To: Scot Doyle <lkml14@...tdoyle.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Michael Kerrisk <mtk.manpages@...il.com>,
Jiri Slaby <jslaby@...e.cz>,
Tomi Valkeinen <tomi.valkeinen@...com>,
Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
Pavel Machek <pavel@....cz>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-kernel@...r.kernel.org, linux-fbdev@...r.kernel.org,
linux-man@...r.kernel.org, linux-api@...r.kernel.org
Subject: Re: [PATCH v2 1/3] vt: add cursor blink interval escape sequence
On 26 Mar 2015 13:54, Scot Doyle wrote:
> Add an escape sequence to specify the current console's cursor blink
> interval. The interval is specified as a number of milliseconds until
> the next cursor display state toggle, from 50 to 65535. /proc/loadavg
> did not show a difference with a one msec interval, but the lower
> bound is set to 50 msecs since slower hardware wasn't tested.
if they want to be crazy, why not let them ? it's not like we generally prevent
the user from destroying their machine. i.e. just require the value to be > 0
(unless you want to let 0 disable things).
-mike
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists