From: Russell King <rmk@arm.linux.org.uk>
To: Frank Torres <frank@ingecom.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Duplicate console output to a RS232C and keep keyb where it is
Date: Fri, 3 Aug 2001 19:43:00 +0100 [thread overview]
Message-ID: <20010803194300.A1609@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.3.95.1010803085542.16919A-100000@chaos.analogic.com> <018201c11c24$cd2af730$66011ec0@frank>
In-Reply-To: <018201c11c24$cd2af730$66011ec0@frank>; from frank@ingecom.net on Fri, Aug 03, 2001 at 04:01:28PM +0200
On Fri, Aug 03, 2001 at 04:01:28PM +0200, Frank Torres wrote:
> > This is not valid. You cannot reasonably have parity and 8 bits. One
> > of them has to go. Either use 8 bits and no parity or 7 bits with
> > parity.
All standard 16550 family ports support 8 bits _and_ parity. Ancient
serial ports did have a restriction, but that restriction is no more.
> All showed wrong or no characters in the display. It only worked with 8,
> parity on, parity odd, stop b. (also with no stop b.)
You actually mean 2 stop bits. (There is _always_ one stop bit).
I read your first mail, but couldn't really grasp the details of your
problem.
Are you trying to direct console _output_ to ttyS2 and the VGA card, yet
still accept input from the PS/2 keyboard? And then when you try to set
this up, you get garbled characters via ttyS2?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-08-03 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 12:27 Duplicate console output to a RS232C and keep keyb where it is Frank Torres
2001-08-03 13:03 ` Richard B. Johnson
2001-08-03 14:01 ` Frank Torres
2001-08-03 14:50 ` Richard B. Johnson
2001-08-03 18:43 ` Russell King [this message]
2001-08-06 7:35 ` Frank Torres
2001-08-06 12:45 ` Richard B. Johnson
2001-08-06 13:12 ` Frank Torres
2001-08-03 22:45 ` J. Dow
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=20010803194300.A1609@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=frank@ingecom.net \
--cc=linux-kernel@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.