From: Sam Song <samlinuxppc@yahoo.com.cn>
To: lonelobo <lonelobo@163.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: I cant stop at the break point !
Date: Mon, 30 May 2005 18:56:29 +0800 (CST) [thread overview]
Message-ID: <20050530105629.68312.qmail@web15801.mail.cnb.yahoo.com> (raw)
In-Reply-To: <429AE4A8.000013.14311@m150.163.com>
--- lonelobo <lonelobo@163.com> wrote:
> hello every one! when I debug the u-boot with
> bdi2000 ,I set the break point at the
> board_init_r but it cannot stop there. I do this as
Two things you need to take care.
First, you sent your message to a wrong maillist.
Questions related u-boot pls go to u-boot maillist.
Second, send your message in plain text to maillist.
HTML is not welcome. Pls adjust your mail preference.
Thanks,
Sam
_________________________________________________________
Do You Yahoo!?
注册世界一流品质的雅虎免费电邮
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/
prev parent reply other threads:[~2005-05-30 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 10:02 I cant stop at the break point ! lonelobo
2005-05-30 10:56 ` Sam Song [this message]
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=20050530105629.68312.qmail@web15801.mail.cnb.yahoo.com \
--to=samlinuxppc@yahoo.com.cn \
--cc=linuxppc-embedded@ozlabs.org \
--cc=lonelobo@163.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