From: Dave Land <xmechanic@landcomp.net>
To: Jeroen Roovers <jer@gentoo.org>, linux-parisc@vger.kernel.org
Cc: Rolf Eike Beer <eike-kernel@sf-tec.de>,
John David Anglin <dave.anglin@bell.net>
Subject: Re: [C8000] serial console drops input
Date: Sat, 25 Jan 2014 12:54:55 -0700 [thread overview]
Message-ID: <52E4168F.1010606@landcomp.net> (raw)
In-Reply-To: <20140125181348.67a2bf8f@marga.jer-c2.orkz.net>
On 1/25/14 10:13 AM, Jeroen Roovers wrote:
> On Sat, 25 Jan 2014 18:03:17 +0100
> Rolf Eike Beer <eike-kernel@sf-tec.de> wrote:
>
>> Boot output looks fine. Cables are normal nullmodem. I can interact
>> using minicom with the firmware, i.e. typing "BO
>> PRI<return>N<return>" or things like that work fine.
>
> Yes, in the PDC everything still seems fine.
>
> But as early as in the IPL I can't paste a string without
> characters dropping (which is how I first noticed the issue, since
> that's where I normally do this to select a kernel to boot). So did the
> IPL change as well, then?
>
>
>
> jer
> --
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
(I probably should have hit reply-all on this before...)
Just as an FYI, I had some of the same behavior when I first set my
J6750 up with a serial line (null modem cable to a secondary machine)
Usually had to type the p/w 2 or 3 times to get it to 'take' in minicom.
One thing I *did* notice was the *length* of the null modem cable and
the proximity of the 2 machines seemed to make a difference (bad cable
shielding maybe?) Just my 2 cents. (Running Kernel Ver. 3.12.6-2 at the
moment)
...and like Dave A. mentioned, Xon/Xoff makes a difference too.
Dave L.
P.S. Now that it's up and running, and I usually log in with PUTTY or
the STIcon graphics console, it's not a problem anymore. :-)
--
Dave Land
Land Computer Service xmechanic@landcomp.net
ICQ: 676030523
next prev parent reply other threads:[~2014-01-25 19:54 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
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 [this message]
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=52E4168F.1010606@landcomp.net \
--to=xmechanic@landcomp.net \
--cc=dave.anglin@bell.net \
--cc=eike-kernel@sf-tec.de \
--cc=jer@gentoo.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.