From: Wolfgang Denk <wd@denx.de>
To: "rick.liu" <dovi@eyou.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: kermit:How to disable the flow control signals?
Date: Sun, 18 May 2003 12:21:55 +0200 [thread overview]
Message-ID: <20030518102200.B44FBC6162@atlas.denx.de> (raw)
In-Reply-To: Your message of "18 May 2003 12:59:03 +0800." <20030518125903.28066.qmail@eyou.com>
Hi,
in message <20030518125903.28066.qmail@eyou.com> you wrote:
>
> >Ummm... why do you bother? Is anything not working?
>
> Yes,my console still outputs nothing,even not a single word.
Maybe your target does not output anything (at least not at the
expected baudrate) ?
> So,I must first make sure it's not my console emulator's problem.
Test with a known to work device first.
> So there is no money for something like BDI.
You pay anyway - either with money for the BDI, or with your time
when you try to do without it.
> As u mentioned before,I will read u-boot source,maybe it's a way of continue
> my
> work.Would u give me a clue of uboot,I mean the sequence of boot and the
> according
> source file?I didnot find this kind of infomation on the internet.
Booting starts at the reset vector, i. e. at _start in cpu/*/start.S
But this is off topic here. Follow-up to u-boot-users, please.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
One does not thank logic.
-- Sarek, "Journey to Babel", stardate 3842.4
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-18 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 4:59 kermit:How to disable the flow control signals? rick.liu
2003-05-18 10:21 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-17 10:45 rick.liu
2003-05-17 17:07 ` Wolfgang Denk
2003-05-17 5:18 rick.liu
2003-05-17 7:29 ` 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=20030518102200.B44FBC6162@atlas.denx.de \
--to=wd@denx.de \
--cc=dovi@eyou.com \
--cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).