From: Wolfgang Denk <wd@denx.de>
To: caixupeng <edmoon@huawei.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ppcboot, ebony , change baudrate function has bug.
Date: Tue, 26 Nov 2002 09:31:59 +0100 [thread overview]
Message-ID: <20021126083204.5EFE8C6134@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 26 Nov 2002 09:44:19 +0800." <001d01c294ed$569cecc0$92690b0a@DBKQW41X>
In message <001d01c294ed$569cecc0$92690b0a@DBKQW41X> you wrote:
>
> when you set a new baudrate,
>
> => setenv baudrate 38400
> ## Switch baudrate to 38400 bps and press ENTER ...
>
>
> it will hang .
It does not hang. It waits for you to switch the baudrate and press
ENTER.
> I find a way to avoid it.
> first, clear the baudrate with "setenv baudrate=xxxx"----it's wrong ,
This is an ugly hack,and strongly discouraged.
The way the baudrate change is implemented in PPCBoot is intentional
- it prevents you to enter a baudrate which you cannot use with your
terminal. If you cannot type the enter and the "saveenv" command
necessary to store the new baudrate permanently, you can always reset
the board ans it will come up with the old, working baudrate.
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
For every problem there is one solution which is simple, neat, and
wrong. - H. L. Mencken
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-11-26 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 1:44 ppcboot, ebony , change baudrate function has bug caixupeng
2002-11-26 8:31 ` Wolfgang Denk [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=20021126083204.5EFE8C6134@atlas.denx.de \
--to=wd@denx.de \
--cc=edmoon@huawei.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).