Linux PARISC architecture development
 help / color / mirror / Atom feed
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 18:03:17 +0100	[thread overview]
Message-ID: <7905648.nun1s37FKj@eto> (raw)
In-Reply-To: <BLU0-SMTP1495AAE1C79CFA59BC915E97A00@phx.gbl>

[-- Attachment #1: Type: text/plain, Size: 466 bytes --]

> > One other thing: the serial line from the C8000 to my Sun Fire V240
> > works
> > flawlessly.
> 
> Same cable?  Does boot output look ok or are characters dropped?
> Which kernels specifically (c8000 can c3600)?

c8000: 3.12.5 minus the mmap patch (the same for 3.12.8)
c3600: 3.12.5

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.

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-01-25 17:03 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 [this message]
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=7905648.nun1s37FKj@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