From: Govindraj <govindraj.ti@gmail.com>
To: "Kittlitz, Edward (Ned)" <ned.kittlitz@alcatel-lucent.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: handling flow control for console device
Date: Tue, 27 Apr 2010 20:09:06 +0530 [thread overview]
Message-ID: <j2id6a0f7aa1004270739l96b8ba58h74d18cb206f47e7b@mail.gmail.com> (raw)
In-Reply-To: <C1859C32A5123B49B7BC37C19355B37A24F842695D@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
On Wed, Apr 21, 2010 at 12:38 AM, Kittlitz, Edward (Ned)
<ned.kittlitz@alcatel-lucent.com> wrote:
> Hello,
>
> I've been trying to figure out the Linux philosophy on
> flow control for console devices.
>
> We have several situations where flow control
> can stop bootup or normal operation. For us, it's more
> important that things keep running; console output has
> lower priority.
>
> I thought there would be some way to forcibly disable
> flow control for the console. But I can not find any way
> to do it. In my case, it's XOFF flow control.
>
During boot up most of tty drivers will be using tty_std_termios settings
when we do an uart_register_driver, init_termios will be set to tty_std_termios.
And looking into tty_std_termios we have
.c_iflag = ICRNL | IXON,
here IXON is enabled by default.
tty_std_termios ---> "drivers/char/tty_io.c"
---
Regards,
Govindraj.R
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-04-27 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 19:08 handling flow control for console device Kittlitz, Edward (Ned)
2010-04-27 14:39 ` Govindraj [this message]
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=j2id6a0f7aa1004270739l96b8ba58h74d18cb206f47e7b@mail.gmail.com \
--to=govindraj.ti@gmail.com \
--cc=linux-serial@vger.kernel.org \
--cc=ned.kittlitz@alcatel-lucent.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;
as well as URLs for NNTP newsgroup(s).