public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] logbuff: Change default console loglevel to 8
Date: Fri, 07 May 2010 11:15:51 +0200	[thread overview]
Message-ID: <m2ocgsax88.fsf@ohwell.denx.de> (raw)
In-Reply-To: <1273189717-26218-1-git-send-email-ptyser@xes-inc.com> (Peter Tyser's message of "Thu, 6 May 2010 18:48:37 -0500")

Hi Peter,

> Previously, a default of 3 was assigned to the console loglevel while
> standard messages had a level of 4.  This resulted in U-Boot's console
> disappearing if a user enabled CONFIG_LOGBUFFER but didn't manually set
> the 'loglevel' environment variable to a value greater than 4.
>
> Setting the default console loglevel to 8 causes all messages to be
> printed to the console, which is standard U-Boot operation.  Users can
> then reduce the console loglevel if they want using the 'loglevel'
> environment variable.

I don't really like that patch as I think it will alter how U-Boot
"looks" (i.e. what it outputs) on e.g. the lwmon5 board where the
logbuffer is used primarily for logging POST results.

Can you please explain to me again, why the messages are not output any
more once CONFIG_LOGBUFFER is enabled?  If 'stdout' is serial (and I
don't see why this should not be the case) then is there already a
problem?

Cheers
  Detlev

-- 
X-Windows has to be the most expensive way ever of popping up an Emacs
window.
                                          -- The UNIX Haters Handbook
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

  reply	other threads:[~2010-05-07  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 23:48 [U-Boot] [PATCH] logbuff: Change default console loglevel to 8 Peter Tyser
2010-05-07  9:15 ` Detlev Zundel [this message]
2010-05-07 17:57   ` Peter Tyser

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=m2ocgsax88.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --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