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.
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
