From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ladislav Michl <ladis@linux-mips.org>
Date: Wed, 29 Jun 2005 20:09:47 +0200
Subject: [U-Boot-Users] silent console, nulldev and CONFIG_AUTOBOOT_KEYED
Message-ID: <20050629180947.GA25852@orphique>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi,

If "silent" env variable is set GD_FLG_SILENT is added to gd->flags
(in console_init_f). That effectively causes all console output to be
suppresed. That flag also causes nulldev to become outputdev
(in console_init_r). Btw, shouldn't CONFIG_SILENT_CONSOLE depend on
CFG_DEVICE_NULLDEV in this case? Now we are entering into abortboot
(CONFIG_AUTOBOOT_KEYED) and because "silent" env variable is set and
also CONFIG_SILENT_CONSOLE defined console_assign (stdout, "serial"); is
called, doing basicaly nothing, because GD_FLG_SILENT which is still
set prevents any console output.

There are various solutions from this situation, but I'd like first
understand what is CFG_DEVICE_NULLDEV good for when we have GD_FLG_SILENT?
Or better, how should all these three things in question behave?

thanks,
	ladis