From: "tauanna@tiscali.it" <tauanna@tiscali.it>
To: linuxppc-embedded@ozlabs.org
Subject: SMC1 serial port blocks
Date: Thu, 29 Jun 2006 23:29:31 +0200 (CEST) [thread overview]
Message-ID: <29672631.1151616571867.JavaMail.root@ps18> (raw)
I have two identical linux boxes connected via a serial link (9600
bit/s without any handshaking). In both boxes the serial port is
realized by SMC1. One box is receiving and the other transmits a long
stream of bytes. If I start the receiver after the transmitter, it
seems that the transmitter cannot send anymore, even when I start the
receiver. The transmitter has to be restarted to solve the problem.
Any help is appreciated,
Anna
Hai voglia di fare un viaggio, ma non sai dove andare?
Scegli una delle nostre offerte HOTEL IN ITALIA E IN EUROPA da 50 euro.
Prenota subito su Expedia.it e... buona vacanza!
http://expedia.viaggi.tiscali.it/default.aspx?eapid=330-8
next reply other threads:[~2006-06-29 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 21:29 tauanna [this message]
2006-06-30 6:34 ` SMC1 serial port blocks Martin Krause
-- strict thread matches above, loose matches on Subject: below --
2006-06-29 21:38 SMC1 Serial " tauanna
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=29672631.1151616571867.JavaMail.root@ps18 \
--to=tauanna@tiscali.it \
--cc=linuxppc-embedded@ozlabs.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).