All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: tty loop-back device
Date: Sat, 28 Sep 2013 16:03:20 +0000 (UTC)	[thread overview]
Message-ID: <l26uk7$id2$2@ger.gmane.org> (raw)
In-Reply-To: l26jrq$48d$1@ger.gmane.org

On 2013-09-28, Matwey V. Kornilov <matwey.kornilov@gmail.com> wrote:

> Not sure whether here is the right place to ask. Do the kernel already 
> has (or, would it be great to have) the tty loop-back support? At least 
> I've not found something appropriate. I mean, imagine kind of /dev/tty 
> device, supporting read/write and termios interface and transferring 
> your read/write/ioctl calls to another user-space application listening, 
> for instance, /dev/tty_loopback_master. Like a named pipe device.

What you're talking about is pretty much the existing pty device.

Unfortunately, Linux pty's only support a subset of the serial port
API, so they can't be used for applications like network-connected
serial ports.  So people like me have to write kernel-mode drivers for
such devices.

I've suggested extending the Linux pty so that it _does_ support the
rest of the serial port API.  I even offered to work on it if the
results would likely be accepted into the kernel tree, but my
questions/offers have never gotten any response.

-- 
Grant




  reply	other threads:[~2013-09-28 16:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28 12:59 tty loop-back device Matwey V. Kornilov
2013-09-28 16:03 ` Grant Edwards [this message]
2013-09-28 17:15   ` Greg KH
2013-09-28 17:21   ` Matwey V. Kornilov
2013-09-28 20:41     ` Matwey V. Kornilov
2013-09-29  3:21       ` Grant Edwards
2013-09-29  7:09         ` Matwey V. Kornilov
2013-09-30 22:28           ` Grant Edwards

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='l26uk7$id2$2@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --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 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.