mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Aubrey Li" <aubreylee@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-serial@vger.kernel.org
Subject: [BUG]: 2.6.19.2: Weird serial core issue
Date: Wed, 31 Jan 2007 18:49:25 +0800	[thread overview]
Message-ID: <6d6a94c50701310249o2b2c8024i4d3f28ec1601246a@mail.gmail.com> (raw)

I insert one printk into drivers/serial/serial_core.c:
uart_set_termios() to describe the issue.
static void uart_set_termios(struct tty_struct *tty, struct termios
*old_termios)
{
 ----snip----
        unsigned int cflag = tty->termios->c_cflag;

        BUG_ON(!kernel_locked());
+++printk("new_termios flag: 0x%x, old_termios flag: 0x%x\n");
+++             cflag, old_termios->c_cflag);

----snip ----
}

When I telnet my board and run the following command:
---- root:~> stty -F /dev/ttyS0 -crtscts

I got the following result from the console of my board:
---- root:~>new_termios flag: 0x1cb1, old_termios flag: 0x80001cb1

That's correct. CRTSCTS flag is clear

But when I type "ENTER" key on the console, I got:
----root:~>new_termios flag: 0x80001cb1, old_termios flag: 0x1cb1

The CRTSCTS flag is set back. But I didn't set it back, I just type "ENTER".
I guess, Is it a serial core bug?

-Aubrey

             reply	other threads:[~2007-01-31 10:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 10:49 Aubrey Li [this message]
2007-01-31 16:21 ` Alan
2007-02-01  2:33   ` Aubrey Li
2007-02-01  9:45     ` Russell King
2007-02-01 10:09       ` Aubrey Li
2007-02-01 11:16         ` Russell King
2007-02-01 17:54           ` Aubrey Li
2007-02-01 19:09             ` Russell King
     [not found]     ` <000201c745d9$4577fe20$2e01a8c0@acksys.local>
2007-02-01 10:38       ` Aubrey Li
2007-02-01 15:19         ` Paul Fulghum
2007-02-01 12:02     ` Alan

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=6d6a94c50701310249o2b2c8024i4d3f28ec1601246a@mail.gmail.com \
    --to=aubreylee@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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

all inboxes | Powered by JetHome®