From: Michael R. Hines <mhines@google.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] logbuffer
Date: Thu, 29 Jun 2006 21:56:03 -0700 [thread overview]
Message-ID: <44A4AEE3.9080400@google.com> (raw)
In-Reply-To: <20060630041214.5469.qmail@web32201.mail.mud.yahoo.com>
That's what my first attempt tried to do, but it didn't seem to work.
I reduced mem_size (I think) inside the bd_info struct by 16K.
Just curious if there was a more properly intended way of going about it...
- Michael
Frank wrote:
> --- "Michael R. Hines" <mhines@google.com> wrote:
>
>
>> I'd like to use the logbuffer functionality in u-boot...
>>
>> After #define'ing CONFIG_LOGBUFFER, I can
>> successfully see our data getting printed to the reserved
>> 16K region in dram. However, we want to grab that data
>> back out after linux has booted.
>>
>> During the various initializations that linux does on boot,
>> (somewhere before init is actually run, I believe), the data
>> in the 16K buffer at the end of dram gets over-written
>> by somebody inside linux, and is lost.
>>
>> I found a thread somewhere on the net where Wolfgang
>> mentioned that linux needed a patch to be told not to
>> intrude on those logbuffer pages, but nothing more than
>> that.
>>
>> Is there a proper way to handle this?
>>
>> Thanks,
>> - Michael R. Hines
>>
>
> I've never used the log buffer before, but I would think you
> could just tell the kernel you have less memory then is
> physically there. That way the kernel wouldn't touch the area
> used by the log buffer...
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
next prev parent reply other threads:[~2006-06-30 4:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 2:01 [U-Boot-Users] logbuffer Michael R. Hines
2006-06-30 4:12 ` Frank
2006-06-30 4:56 ` Michael R. Hines [this message]
2006-06-30 5:05 ` Frank
2006-07-06 21:28 ` Michael R. Hines
2006-06-30 7:01 ` 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=44A4AEE3.9080400@google.com \
--to=mhines@google.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 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.