From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Kernel patch for CONFIG_LOGBUFFER
Date: Mon, 29 Jun 2009 13:23:27 +0200 [thread overview]
Message-ID: <m28wjb472o.fsf@ohwell.denx.de> (raw)
In-Reply-To: <39A385F269A9E349AA6606AD4E327D761C590656@BEL1EXCH02.amer.sfnt.local> (Serguei Evseev's message of "Sat, 27 Jun 2009 20:57:37 -0400")
Hi Serguei,
> I'm looking for a working patch for the Linux kernel 2.6.28.8 that
> would allow using CONFIG_LOGBUFFER (a kernel log buffer shared between
> U-Boot and the kernel). I'm using u-boot 1.3.3. When LOGBUFFER is
> enabled in the kernel configuration the kernel build fails with:
> kernel/built-in.o: In function `setup_ext_logbuff': : undefined
> reference to `setup_ext_logbuff_mem'
This is to be expected - CONFIG_LOGBUFFER only worked with arch/ppc. It
is broken since the arch/ppc removal and nobody (yet) cared to get it to
life again. Only recently there were discussions on the linux-embedded
ml[1] which may yield other solutions going mainline.
> Could anybody also tell me how the buffer location (I think the size
> is fixed to 16K) is communicated to the kernel, via a kernel command
> line parameter? If so, what is it?
It was placed at a known address relative to the end of RAM. Check
arch/ppc/mm/init.c e.g. in our DENX-v2.6.25-stable branch.
Cheers
Detlev
[1] http://www.mail-archive.com/linux-embedded at vger.kernel.org/msg01945.html
--
Computers are useless. They can only give you answers.
-- Pablo Picasso
--
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
next prev parent reply other threads:[~2009-06-29 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 0:57 [U-Boot] Kernel patch for CONFIG_LOGBUFFER Evseev, Serguei
2009-06-29 11:23 ` Detlev Zundel [this message]
2009-06-29 17:55 ` Evseev, Serguei
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=m28wjb472o.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