From: Dan Malek <dan@embeddededge.com>
To: "Joakim Tjernlund" <joakim.tjernlund@lumentis.se>
Cc: "Linuxppc-Embedded@Lists. Linuxppc. Org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Serial port text corruption
Date: Tue, 18 May 2004 12:56:02 -0400 [thread overview]
Message-ID: <3EECAC02-A8EC-11D8-BBC2-003065F9B7DC@embeddededge.com> (raw)
In-Reply-To: <JPEALJAFNGDDLOPNDIEECEJBCIAA.joakim.tjernlund@lumentis.se>
On May 18, 2004, at 6:03 AM, Joakim Tjernlund wrote:
> This is very confusing and I would fix it but I don't know where to
> start.
> Any guesses as to where the problem is? Kernel serial layer, the 8xx
> uart.c driver,
> the user space login program or somewhere else?
Are you using a USB to serial adapter on your laptop? I've seen similar
things on many different systems only to trace down problems with the
USB/serial adapter and the host terminal emulation program. Find some
computer with a real serial port and ensure it fails the same way.
On the other hand, many. many years ago when the 8xx uart driver was
written we added some delays during mode changes (which happens
during this phase of the log in) to ensure all of the CPM fifos were
drained
properly. Again, this wasn't exactly the SMC problem, but shifting out
bits
that didn't look proper messed up the host serial interface. Maybe
during
all of the recent updates to the drivers people "optimized" things not
knowing
their effects.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-18 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 10:03 Serial port text corruption Joakim Tjernlund
2004-05-18 16:56 ` Dan Malek [this message]
2004-05-18 21:05 ` Joakim Tjernlund
2004-05-19 15:49 ` Joakim Tjernlund
2004-05-19 16:47 ` Dan Malek
2004-05-19 17:14 ` Joakim Tjernlund
2004-05-19 17:05 ` Mark Chambers
-- strict thread matches above, loose matches on Subject: below --
2004-05-18 12:31 VanBaren, Gerald (AGRE)
2004-05-18 21:17 ` Joakim Tjernlund
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=3EECAC02-A8EC-11D8-BBC2-003065F9B7DC@embeddededge.com \
--to=dan@embeddededge.com \
--cc=joakim.tjernlund@lumentis.se \
--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).