From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dennis Ruffer <daruffer@gmail.com>
Date: Wed, 5 May 2010 12:22:04 -0700
Subject: [U-Boot] Endless loop in cmd_log.c?
In-Reply-To: <1273069733-6194-4-git-send-email-weisserm@arcor.de>
References: <1273069733-6194-1-git-send-email-weisserm@arcor.de>	<1273069733-6194-2-git-send-email-weisserm@arcor.de>	<1273069733-6194-3-git-send-email-weisserm@arcor.de>
	<1273069733-6194-4-git-send-email-weisserm@arcor.de>
Message-ID: <012501caec88$40387670$c0a96350$@com>
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

I am trying to implement CONFIG_LOGBUFFER and CONFIG_CMD_LOG on our ARM
systems and I seem to have run into an endless loop.  With loglevel=5 so we
still see our console output, the printf at the end of logbuff_printk
appears to create an endless loop.

I had to replace that line with serial_puts(msg);

Have I missed some other solution or do the systems that use this never set
logbuffer higher than default_message_loglevel?

DaR