From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc@vger.kernel.org
Subject: Re: [C8000] serial console drops input
Date: Sat, 25 Jan 2014 17:34:14 +0100 [thread overview]
Message-ID: <1417398.fmUESL4Ngr@eto> (raw)
In-Reply-To: <BLU0-SMTP74DD0D86114628AE2FE0A297A00@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
Am Samstag 25 Januar 2014, 11:29:22 schrieb John David Anglin:
> On 25-Jan-14, at 3:20 AM, Rolf Eike Beer wrote:
> > Am Samstag, 25. Januar 2014, 05:41:44 schrieben Sie:
> >> In recent kernels, with the new serial console code for the C8000,
> >> performance is terrible. Typing quickly results in characters getting
> >> dropped (I have no idea where I lose them), pasting results in 9
> >> out of
> >> 10 characters being dropped, and I don't see anything on the client
> >> side that could cause this, and I never had this problem with the old
> >> ttyB0 code. While entering a password, some characters never turn
> >> up on
> >> the other side and some get echoed back to the client.
> >>
> >> Is anyone else seeing this?
> >
> > What I see is that the C3600 now finally sees the kernel/console
> > output of the
> > C8000, I also see the login prompt, but typing anything on the C3600
> > doesn't
> > seem to make it to the C8k. So things have improved, I now can
> > actually see
>
> Is XON/XOFF enabled in your terminal program? See c8000 Technical
> Reference
> Guide for setup requirements
>
> I'm using standard PC null modem cable from c3750 to c8000 and minicom
> 2.7. It works
> fine but it's fairly slow.
Both on and off doesn't make a difference.
One other thing: the serial line from the C8000 to my Sun Fire V240 works
flawlessly.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-01-25 16:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 4:41 [C8000] serial console drops input Jeroen Roovers
2014-01-25 8:20 ` Rolf Eike Beer
2014-01-25 16:29 ` John David Anglin
2014-01-25 16:34 ` Rolf Eike Beer [this message]
2014-01-25 16:50 ` John David Anglin
2014-01-25 17:03 ` Rolf Eike Beer
2014-01-25 17:13 ` Jeroen Roovers
2014-01-25 19:54 ` Dave Land
2014-01-25 20:04 ` Dave Land
2014-01-25 20:13 ` John David Anglin
2014-01-26 0:02 ` Jeroen Roovers
2014-01-26 1:01 ` Dave Land
2014-01-26 15:07 ` Helge Deller
2014-01-26 20:22 ` Jeroen Roovers
2014-01-26 20:35 ` Dave Land
2014-01-26 21:01 ` John David Anglin
2014-01-26 21:04 ` John David Anglin
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=1417398.fmUESL4Ngr@eto \
--to=eike-kernel@sf-tec.de \
--cc=linux-parisc@vger.kernel.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