From: Disconnect <dis@sigkill.net>
To: Marc Karasek <marc_karasek@ivivity.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Bug in serial.c
Date: Thu, 19 Apr 2001 11:38:54 -0400 [thread overview]
Message-ID: <20010419113854.D16472@sigkill.net> (raw)
In-Reply-To: <25369470B6F0D41194820002B328BDD27C8E@ATLOPS>
In-Reply-To: <25369470B6F0D41194820002B328BDD27C8E@ATLOPS>
On Thu, 19 Apr 2001, Marc Karasek did have cause to say:
> 2) In 2.4.3 the console port using ttySX is broken. It dumps fine to the
> terminal but when you get to a point of entering data (login, configuration
> scripts, etc) the terminal does not accept any input.
Most gettys and such take a /dev/tty* argument, which has to be changed to
point to the serial port for a serial console. Config scripts (and
anything else) specifically using /dev/tty or /dev/console should work
fine, however. (I wouldn't recommend pointing a getty at /dev/console - we
had some issues on a headless server trying that. Easiest to point it at
/dev/ttyS0 or whatnot.)
>
> So far I have been able to debug to the point where I see that the kernel is
> receiving the characters from the serial.c driver. But it never echos them
> or does anything else with them. I will continue to look into this at this
> end.
>
> I was also wondering if anyone else has seen this or if a patch is avail for
> this bug??
>
> Marc Karasek
> Sr. Firmware Engineer
> iVivity Inc
> marc_karasek@ivivity.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
---
_.-=<Disconnect>=-._
| dis@sigkill.net | And Remember...
\ shawn@healthcite.com / He who controls Purple controls the Universe..
PGP Key given on Request Or at least the Purple parts!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1 [www.ebb.org/ungeek]
GIT/CC/CM/AT d--(-)@ s+:-- a-->? C++++$ ULBS*++++$ P+>+++ L++++>+++++
E--- W+++ N+@ o+>$ K? w--->+++++ O- M V-- PS+() PE Y+@ PGP++() t 5---
X-- R tv+@ b++++>$ DI++++ D++(+++) G++ e* h(-)* r++ y++
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~2001-04-19 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 15:32 Bug in serial.c Marc Karasek
2001-04-19 15:38 ` Disconnect [this message]
2001-04-19 15:43 ` Richard B. Johnson
2001-04-19 23:10 ` Steven Walter
2001-04-20 16:31 ` Fabrice Gautier
-- strict thread matches above, loose matches on Subject: below --
2001-04-19 16:18 Marc Karasek
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=20010419113854.D16472@sigkill.net \
--to=dis@sigkill.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marc_karasek@ivivity.com \
/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