All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: the usage of hardware flow control in serial console
Date: Tue, 1 Jun 2021 06:49:18 +0200	[thread overview]
Message-ID: <YLW8Th/dbKBs1Ntk@kroah.com> (raw)
In-Reply-To: <60B59E0F.7030609@fujitsu.com>

On Tue, Jun 01, 2021 at 02:39:41AM +0000, xuyang2018.jy@fujitsu.com wrote:
> HI All
> 
> I append "console=ttyS0,115200n8r" to my kernel command line and reboot
> my system.
> 
> # cat /proc/tty/driver/serial
> serinfo:1.0 driver revision:
> 0: uart:16550A port:000003F8 irq:4 tx:0 rx:0 RTS|DTR
> 1: uart:unknown port:000002F8 irq:3
> 2: uart:unknown port:000003E8 irq:4
> 3: uart:unknown port:000002E8 irq:3
> 
> then I echo 1 > /dev/ttyS0, but it hangs.(If I don't use r, it works well.)

'echo' is horrible at testing serial port communication.  Why not use a
real serial terminal program that knows how to set the line settings?

> Does it need my console connected with other machine?

Something needs to be on the other end of that serial connection for
this to work properly, right?

> Also, many services become timeout when I use systemctl
> restart/status/stop(tx,rx data doesn't increase).
> 
> I just want to check whether it is a usage problem(my system environmet
> is centos8). My machine is physical machine and virtual machine doesn't
> have this problem(it has RTS|CTS|DTR|DSR|CD flag).

Why do you want to use "r" here?  What problem are you trying to solve?

thanks,

greg k-h

      reply	other threads:[~2021-06-01  4:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  2:39 the usage of hardware flow control in serial console xuyang2018.jy
2021-06-01  4:49 ` Greg KH [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=YLW8Th/dbKBs1Ntk@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=xuyang2018.jy@fujitsu.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 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.