From f72da3406bf6f1c1bce9aa03b07d070413a916af Mon Sep 17 00:00:00 2001 From: wdenk Date: Fri, 10 Oct 2003 10:05:42 +0000 Subject: Added config option CONFIG_SILENT_CONSOLE. See doc/README.silent for more information --- doc/README.silent | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/README.silent (limited to 'doc/README.silent') diff --git a/doc/README.silent b/doc/README.silent new file mode 100644 index 0000000000..f2628a6bf8 --- /dev/null +++ b/doc/README.silent @@ -0,0 +1,22 @@ +The config option CONFIG_SILENT_CONSOLE can be used to quiet messages +on the console. If the option has been enabled, the output can be +silenced by setting the environment variable "silent". The variable +is latched into the global data at an early stage in the boot process +so deleting it with "setenv" will not take effect until the system is +restarted. + +The following actions are taken if "silent" is set at boot time: + + - Until the console devices have been initialized, output has to be + suppressed by testing for the flag "GD_FLG_SILENT" in "gd->flags". + Currently only the messages for the TRAB board are handled in this + way. + + - When the console devices have been initialized, "stdout" and + "stderr" are set to "nulldev", so subsequent messages are + suppressed automatically. Make sure to enable "nulldev" by + #defining CFG_DEVICE_NULLDEV in your board config file. + + - When booting a linux kernel, the "bootargs" are fixed up so that + the argument "console=" will be in the command line, no matter how + it was set in "bootargs" before. -- cgit v1.2.1