From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Turning off automatic screen clanking
Date: Mon, 28 Jul 2003 16:00:03 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0307281555400.27569@chaos> (raw)
I have experimentally determined that I can turn off
the automatic screen blanking with the following escape
sequence.
const char blk[]={27, '[', '9', ';', '0', ']', 0};
main()
{
printf(blk);
}
I need to know what the appropriate ioctl() is to do this
directly without using escape sequences. I have searched
the 2.4.20 sources and can't find any documentation for
anything that remotely even looks like it turns off the
automatic blanking. The code appears to be truly magic.
This is important for some imbeded systems because there
isn't any input available, and the screen output gets shut
off and can't be turned on except by re-booting.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next reply other threads:[~2003-07-28 19:56 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 20:00 Richard B. Johnson [this message]
2003-07-28 20:01 ` Turning off automatic screen clanking Ben Collins
2003-07-28 20:08 ` Frank v Waveren
2003-07-28 20:25 ` Richard B. Johnson
2003-07-28 20:45 ` Charles Lepple
2003-07-29 11:06 ` Richard B. Johnson
2003-07-29 16:51 ` James Simmons
2003-07-29 17:01 ` Andries Brouwer
2003-07-29 17:54 ` Richard B. Johnson
2003-07-29 18:31 ` Alan Cox
2003-07-30 0:17 ` Zwane Mwaikambo
2003-07-30 1:25 ` Jamie Lokier
2003-07-30 1:37 ` Zwane Mwaikambo
2003-07-30 7:14 ` Alex Riesen
2003-07-30 8:00 ` David Lang
2003-07-31 14:33 ` Timothy Miller
2003-07-31 14:57 ` Zwane Mwaikambo
2003-07-31 15:20 ` Jamie Lokier
2003-07-31 21:41 ` Zwane Mwaikambo
2003-08-01 15:25 ` Jamie Lokier
2003-08-01 17:11 ` Zwane Mwaikambo
2003-07-30 1:40 ` Petr Vandrovec
2003-07-30 2:35 ` Petr Vandrovec
2003-07-30 5:22 ` Ville Herva
2003-07-30 5:44 ` Gene Heskett
2003-07-31 14:36 ` Timothy Miller
2003-07-31 16:20 ` Herbert Pötzl
2003-07-31 16:56 ` Mike Dresser
2003-07-31 19:55 ` Timothy Miller
2003-07-31 23:35 ` Ian Hastie
2003-07-30 6:03 ` jw schultz
2003-07-30 2:16 ` Miles Bader
2003-07-30 5:45 ` jw schultz
2003-07-28 20:19 ` Samuel Thibault
2003-07-28 20:27 ` Andries Brouwer
2003-07-29 13:02 Andries.Brouwer
2003-07-29 13:53 ` Richard B. Johnson
2003-07-29 13:56 Andries.Brouwer
2003-07-30 6:14 Erik Andersen
2003-07-30 13:07 ` Richard B. Johnson
2003-07-31 19:15 ` Norberto BENSA
2003-07-31 21:50 ` Zwane Mwaikambo
2003-07-31 20:08 Petr Vandrovec
[not found] <eFZJ.6X7.29@gated-at.bofh.it>
[not found] ` <eH5i.7XC.15@gated-at.bofh.it>
[not found] ` <eNaA.4vE.1@gated-at.bofh.it>
[not found] ` <eRHk.85K.5@gated-at.bofh.it>
[not found] ` <fmBF.48z.41@gated-at.bofh.it>
[not found] ` <fotH.5J2.17@gated-at.bofh.it>
[not found] ` <frB6.8gE.7@gated-at.bofh.it>
2003-08-03 10:40 ` Julien Oster
2003-08-04 0:56 ` Ian Hastie
2003-08-05 18:52 ` Timothy Miller
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=Pine.LNX.4.53.0307281555400.27569@chaos \
--to=root@chaos.analogic.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).