From: Karl-Heinz Krempels <charlie@pool.informatik.rwth-aachen.de>
To: Sid <sid@siddhartha.8m.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: MPC860 - minicom
Date: Mon, 26 Feb 2001 13:25:13 +0100 (MET) [thread overview]
Message-ID: <Pine.SOL.4.10.10102261324080.29120-100000@jennifer.informatik.rwth-aachen.de> (raw)
In-Reply-To: <004501c09fa4$df5fe2f0$2501000a@sid>
Hi,
please check your cables. I think its a handshaking problem.
\Charlie.
Karl-Heinz Krempels, Vereinsstrasse 13-15, 52062 Aachen, +49-241-4093691
Aachen University of Technology , charlie@pool.informatik.rwth-aachen.de
- In a world without walls and fences,
what should we do with windows and gates?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-26 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 3:33 MPC860 - minicom Sid
2001-02-26 12:25 ` Karl-Heinz Krempels [this message]
2001-02-26 17:06 ` MBX860 " Sid
2001-02-28 2:14 ` MBX860 - minicom trouble continues Sid
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=Pine.SOL.4.10.10102261324080.29120-100000@jennifer.informatik.rwth-aachen.de \
--to=charlie@pool.informatik.rwth-aachen.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sid@siddhartha.8m.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;
as well as URLs for NNTP newsgroup(s).