[U-Boot] Antw: Re: U-Boot doesn't silent the output
Frank Ihle
frank.ihle at hs-offenburg.de
Tue Mar 18 11:10:18 CET 2014
>I think preferred behavior for this may be to instead leave any
>'console' arguments as they are and instead ensure that 'quiet' or
>'loglevel=1' is present instead. There are two motivations for doing
>this - the first is that when using a lower loglevel you still get
>suppressed kernel output - but you also get any errors. Thus if
>something goes wrong you'll see why rather than wonder if U-Boot even
>started the kernel. The second is that I've seen a few times in the
>past where setting console to nothing (console=) results in strange
>behavior (it once increased boot time). After all we want a console we
>just don't want to use it as much. I can provide a patch for this if
>you think you may take it?
>
>Thanks,
>
>Andrew Murray
Well let me tell you about the circumstances:
I
use these Images for an embedded system without any console at all, but
of a serial debug port (for developing). So if the development phase is
finished then I really need absolutely no output in any boot sequence
or anytime later, since nobody will read it at all. Because, the actual
aim: I want to have my system booting as fast as any possible, that
means excluding all unused features (here: it's the output).
Now, if you think the patch you mentioned could help me, by disabling all
output but keep everything else in the same way as it was, then I would
really appreciate that if you could share it.
Thank you
More information about the U-Boot
mailing list