From: Ladislav Michl <ladis@linux-mips.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] silent console, nulldev and CONFIG_AUTOBOOT_KEYED
Date: Wed, 29 Jun 2005 20:09:47 +0200 [thread overview]
Message-ID: <20050629180947.GA25852@orphique> (raw)
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
next reply other threads:[~2005-06-29 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 18:09 Ladislav Michl [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-29 22:24 [U-Boot-Users] silent console, nulldev and CONFIG_AUTOBOOT_KEYED Dave Ellis
2005-06-30 7:56 ` Ladislav Michl
2005-06-30 21:43 ` Dave Ellis
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=20050629180947.GA25852@orphique \
--to=ladis@linux-mips.org \
--cc=u-boot@lists.denx.de \
/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