From: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>
To: linux-serial@vger.kernel.org
Subject: tty loop-back device
Date: Sat, 28 Sep 2013 16:59:47 +0400 [thread overview]
Message-ID: <l26jrq$48d$1@ger.gmane.org> (raw)
Hi,
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.
The idea behind that is there are a lot of devices like RS232/485
network ports, for instance:
http://www.moxa.com/product/nport_5110.htm
http://www.lantronix.com/device-networking/embedded-device-servers/xport.html
http://gridconnect.com/rs485-ethernet.html
They are just network devices which transfer kind of telnet protocol
into their-own UARTs.
At the other hand, you have user-space application that wants to operate
with tty serial device. And since there is standard termios interface in
kernel, the user-space application don't care whether the serial port is
real UART, usb-serial, AMBA, etc. We can transparently swap our
hardware. That is not always the case when you use networked serial and
have to communicate over IP.
Moxa NPort kernel driver is implemented in the way I am talking about
(if I understand the code correctly). There is daemon application
communicating with the IP network and putting data received back to the
kernel.
next reply other threads:[~2013-09-28 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 12:59 Matwey V. Kornilov [this message]
2013-09-28 16:03 ` tty loop-back device Grant Edwards
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='l26jrq$48d$1@ger.gmane.org' \
--to=matwey.kornilov@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 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).