blob: 70202cece97fe8a53b49251ca8f64a9cef26ee1e [file] [log] [blame]
wdenkf72da342003-10-10 10:05:42 +00001The config option CONFIG_SILENT_CONSOLE can be used to quiet messages
2on the console. If the option has been enabled, the output can be
Joe Hershbergere080d542012-12-11 22:16:30 -06003silenced by setting the environment variable "silent".
4
5- CONFIG_SILENT_CONSOLE_UPDATE_ON_SET
6 When the "silent" variable is changed with env set, the change
7 will take effect immediately.
8
9- CONFIG_SILENT_CONSOLE_UPDATE_ON_RELOC
10 Some environments are not available until relocation (e.g. NAND)
11 so this will make the value in the flash env take effect at
12 relocation.
wdenkf72da342003-10-10 10:05:42 +000013
14The following actions are taken if "silent" is set at boot time:
15
16 - Until the console devices have been initialized, output has to be
17 suppressed by testing for the flag "GD_FLG_SILENT" in "gd->flags".
wdenkf72da342003-10-10 10:05:42 +000018
19 - When the console devices have been initialized, "stdout" and
20 "stderr" are set to "nulldev", so subsequent messages are
21 suppressed automatically. Make sure to enable "nulldev" by
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +020022 #defining CONFIG_SYS_DEVICE_NULLDEV in your board config file.
wdenkf72da342003-10-10 10:05:42 +000023
24 - When booting a linux kernel, the "bootargs" are fixed up so that
25 the argument "console=" will be in the command line, no matter how
26 it was set in "bootargs" before.