From: Sam Song <samlinuxppc@yahoo.com.cn>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 824x sandpoint and 2.6.x
Date: Sat, 23 Apr 2005 20:16:45 +0800 (CST) [thread overview]
Message-ID: <20050423121645.63553.qmail@web15810.mail.cnb.yahoo.com> (raw)
"Mark A. Greer" <mgreer@mvista.com> wrote:
> >had, is it possible to flush the content of
__log_buf
> >after reset?
>
> Sam,
>
> I thought I finally noticed yesterday that you're
> using 2.4. If that is
> the case, you want to dump "log_buf" not
> "__log_buf".
Uh, I copy the above note to this thread to
continue:-)
The turth is that I ported denx 2.4.24 successfully on
my board
and try to port it to 2.6.x. To my understanding,
UART init was
bad for some reason. It was auto configured as 16450
rather than
16550A as 2.4. Besides, ttyS0 iomem base address in
2.6 is different
to the one in 2.4 although they have the same serial
address setting.
I wander which kind of possiblity coud lead to this
result or even better
to point out some useful printk locations to me.
If possible, could you pls show me a right 2.6 boot
process of
sandpoint X3/2? I wanna to find out some nice hints
of it. This
is the first time to me so hard to debug a kernel
before normal
console.
Thanks a lot,
Sam
_________________________________________________________
Do You Yahoo!?
150万曲MP3疯狂搜,带您闯入音乐殿堂
http://music.yisou.com/
美女明星应有尽有,搜遍美图、艳图和酷图
http://image.yisou.com
1G就是1000兆,雅虎电邮自助扩容!
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/
next reply other threads:[~2005-04-23 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 12:16 Sam Song [this message]
2005-04-29 0:44 ` 824x sandpoint and 2.6.x Mark A. Greer
2005-05-09 11:53 ` Sam Song
-- strict thread matches above, loose matches on Subject: below --
2005-04-30 5:33 Sam Song
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=20050423121645.63553.qmail@web15810.mail.cnb.yahoo.com \
--to=samlinuxppc@yahoo.com.cn \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mgreer@mvista.com \
/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