From: Scott Wood <scottwood@freescale.com>
To: "Sauce.Cheng" <chmhou@sina.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: issue at the beginning of kernel booting
Date: Tue, 07 Apr 2009 14:41:48 -0500 [thread overview]
Message-ID: <49DBAC7C.5040405@freescale.com> (raw)
In-Reply-To: <22930588.post@talk.nabble.com>
Sauce.Cheng wrote:
>>> i tried
>>> CONFIG_PPC_EARLY_DEBUG_CPM=y
>>> CONFIG_PPC_EARLY_DEBUG_CPM_ADDR=0xf00000008
>>> how can i make sure CPM_ADDR, 0xf0000008 is default value
>
>> Look at the u-boot source, or dump the memory and see if it looks like a
>> ring buffer.
>
> sorry, i mean that CPM_ADDR is address of what? address of CPM registers or
> something?
It's the address of a transmit descriptor for the serial port. It's
typically in DPRAM, but the exact position depends on where u-boot put
it. Try 0xf0000088.
>> This is a dts-v0 tree, which implies it's fairly old.
> dose later dts be used in corresponding kernel version ?
Yes, current kernels use dts-v1.
> in addition, there is one more question.
> my RAM size is 32MBytes, my "vmlinux" size is 30MBytes, "vmlinux.o" size is
> 58MBytes. so , will there be something wrong at uncompressing time ?
That's just debugging information; it won't end up in the uImage. Use
the "size" utility in your toolchain to see how big the actual code and
data are.
-Scott
next prev parent reply other threads:[~2009-04-07 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 8:36 issue at the beginning of kernel booting chmhou
2009-03-27 16:15 ` Scott Wood
2009-04-01 15:00 ` Sauce.Cheng
2009-04-02 3:23 ` Sauce.Cheng
2009-04-02 16:12 ` Scott Wood
2009-04-02 21:54 ` Benjamin Herrenschmidt
2009-04-07 14:39 ` Sauce.Cheng
2009-04-07 19:41 ` Scott Wood [this message]
2009-04-07 15:02 ` Sauce.Cheng
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=49DBAC7C.5040405@freescale.com \
--to=scottwood@freescale.com \
--cc=chmhou@sina.com \
--cc=linuxppc-dev@ozlabs.org \
/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.