From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: Fix staircase effect on Altix serial console.
Date: Wed, 03 Mar 2004 22:21:16 +0000 [thread overview]
Message-ID: <20040303222116.GA5481@sgi.com> (raw)
In-Reply-To: <je1xoa7qtb.fsf@sykes.suse.de>
On Wed, Mar 03, 2004 at 12:44:49PM -0800, Jesse Barnes wrote:
> On Wed, Mar 03, 2004 at 06:36:21PM +0100, Andreas Schwab wrote:
> > > I've filed a bug with our system controller group to make the behavior
> > > of the L2 and L1 system controllers consistent (I believe you're using
> > > an L1), which I think is the proper fix.
> >
> > No, it is the *wrong* thing to do. If you do stty -onlcr you should get
> > just one NL, nothing else. It's the job of the tty layer and the serial
> > console write function to translate NL to CRNL, nobody else should mangle
> > the output in any way.
>
> Right, that's why I'm saying that the l2 shouldn't mangle output, nor
> should the PROM. They should just pass through whatever the serial
> driver hands them. I think we're in agreement here?
Sorry, I should have been clearer: our L2 system controller will be
fixed to *not* add CRs, as will our PROM, so we'll need your fix.
David, can you please apply it? Sorry for the runaround.
Andreas, does that sound right?
Thanks,
Jesse
next prev parent reply other threads:[~2004-03-03 22:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 23:49 Fix staircase effect on Altix serial console Andreas Schwab
2004-03-03 2:56 ` David Mosberger
2004-03-03 3:31 ` Jesse Barnes
2004-03-03 10:57 ` Andreas Schwab
2004-03-03 12:46 ` Robin Holt
2004-03-03 13:34 ` Andreas Schwab
2004-03-03 13:40 ` Robin Holt
2004-03-03 14:20 ` Andreas Schwab
2004-03-03 15:11 ` Robin Holt
2004-03-03 15:52 ` Andreas Schwab
2004-03-03 17:19 ` Jesse Barnes
2004-03-03 17:27 ` Jesse Barnes
2004-03-03 17:36 ` Andreas Schwab
2004-03-03 20:44 ` Jesse Barnes
2004-03-03 22:21 ` Jesse Barnes [this message]
2004-03-03 22:28 ` David Mosberger
2004-03-04 11:02 ` Andreas Schwab
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=20040303222116.GA5481@sgi.com \
--to=jbarnes@sgi.com \
--cc=linux-ia64@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