From: Cam <camilo@mesias.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Command line parsing question
Date: Fri, 12 Mar 2004 02:47:30 +0000 [thread overview]
Message-ID: <405124C2.7070607@mesias.co.uk> (raw)
In-Reply-To: <20040312005135.66EB9C0655@atlas.denx.de>
Wolfgang
>>When I type in commands at the command prompt and hit enter, some of the
>>commands are getting run twice.
>
>
> U-Boot just executes the commands it gets told.
[...]
> I know this problem well. I have seen it before. Your terminal server
> is misconfigured. We use a couple of terminal servers ourself, and
> for example I never got a MAXSERVER running correctly.
I don't have a solution but have seen exactly the same problems with
uboot-1.0.0, custom 8270 based board. The terminal server in question is
the one built into the otherwise excellent BDI2000 probe.
We chose to put up with the quirks as they are only ever seen in
development (not deployment).
Regards,
-Cam
next prev parent reply other threads:[~2004-03-12 2:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 23:41 [U-Boot-Users] Command line parsing question Jeff Angielski
2004-03-12 0:51 ` Wolfgang Denk
2004-03-12 2:47 ` Cam [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-12 0:30 Rune Torgersen
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=405124C2.7070607@mesias.co.uk \
--to=camilo@mesias.co.uk \
--cc=u-boot@lists.denx.de \
/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