From: Dennis Ruffer <daruffer@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Endless loop in cmd_log.c?
Date: Wed, 5 May 2010 21:20:10 -0700 [thread overview]
Message-ID: <002701caecd3$6bb4b520$431e1f60$@com> (raw)
In-Reply-To: 1273069733-6194-4-git-send-email-weisserm@arcor.de
Not sure why this hasn't come through in my 2 earlier attempts...
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
next prev parent reply other threads:[~2010-05-06 4:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 14:28 [U-Boot] [PATCH V2 0/3] Add support for MB86R0x SoCs Matthias Weisser
2010-05-05 14:28 ` [U-Boot] [PATCH V2 1/3] arm: " Matthias Weisser
2010-05-05 14:28 ` [U-Boot] [PATCH V2 2/3] video: add support for display controller in " Matthias Weisser
2010-05-05 14:28 ` [U-Boot] [PATCH V2 3/3] arm: Add support for jadecpu board based on MB86R01 SoC Matthias Weisser
2010-05-05 19:22 ` [U-Boot] Endless loop in cmd_log.c? Dennis Ruffer
2010-05-06 23:27 ` Peter Tyser
2010-05-07 0:04 ` Dennis Ruffer
2010-05-07 0:15 ` Peter Tyser
2010-05-07 8:18 ` Detlev Zundel
2010-05-05 21:34 ` Dennis Ruffer
2010-05-06 4:20 ` Dennis Ruffer [this message]
2010-05-06 16:03 ` Dennis Ruffer
2010-05-06 16:21 ` Peter Tyser
2010-05-06 17:51 ` Dennis Ruffer
2010-05-06 18:05 ` Peter Tyser
2010-06-12 9:36 ` [U-Boot] [PATCH V2 3/3] arm: Add support for jadecpu board based on MB86R01 SoC Anatolij Gustschin
2010-06-12 9:28 ` [U-Boot] [PATCH V2 2/3] video: add support for display controller in MB86R0x SoCs Anatolij Gustschin
2010-06-12 9:19 ` [U-Boot] [PATCH V2 1/3] arm: Add support for " Anatolij Gustschin
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='002701caecd3$6bb4b520$431e1f60$@com' \
--to=daruffer@gmail.com \
--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