All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] about to CONFIG_LOGBUFFER ..
Date: Thu, 05 Aug 2004 09:59:43 +0200	[thread overview]
Message-ID: <20040805075948.5DAEDC109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 05 Aug 2004 16:01:38 +0900." <4111DB52.40308@newmi.co.kr>

In message <4111DB52.40308@newmi.co.kr> you wrote:
> I do not understand the CONFIG_LOGBUFFER.
> What's the CONFIG_LOGBUFFER?

It's a feature so that both U-Boto and Linux can use the same memory as log buffer.

> How to use the CONFIG_LOGBUFFER in U-Boot and Linux Kernel?

In U-Boot, for example the POST code can output messages to  the  log
buffer.  Or  you  can  redirect  the standard output of (some or all)
commands to be stored in the log buffer.

In Linux, the syslog mechanism makes use of the log buffer.

This way you can for example have the standard Linux systlog  toolset
process  the  boot  messages  or  the  POST diagnosis. Or you can use
U-Boot to print the Linux kernels log buffer after a crash.

> Why that excluded log buffer in linux system memory?

This is to make sure that the log buffer is kept intact over reboots.
Even after a Linux crash you can use U-Boot (or Linux after the  next
boot) to print the log buffer contents.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
"Pull the wool over your own eyes!"                - J.R. "Bob" Dobbs

  reply	other threads:[~2004-08-05  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  7:01 [U-Boot-Users] about to CONFIG_LOGBUFFER Yongdae, Shin
2004-08-05  7:59 ` Wolfgang Denk [this message]
     [not found] <4111F858.6080206@newmi.co.kr>
2004-08-05 10:12 ` Wolfgang Denk

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=20040805075948.5DAEDC109F@atlas.denx.de \
    --to=wd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.