From: Rodolfo Giometti <giometti@enneenne.com>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: linux-kernel@vger.kernel.org,
Russell Coker <russell@coker.com.au>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: Network Virtual Terminal
Date: Wed, 5 Jan 2011 16:23:13 +0100 [thread overview]
Message-ID: <20110105152313.GC3937@enneenne.com> (raw)
In-Reply-To: <201101041813.49759.hpj@urpla.net>
On Tue, Jan 04, 2011 at 06:13:46PM +0100, Hans-Peter Jansen wrote:
> Dear Rodolfo,
>
> On Monday 03 January 2011, 16:15:34 Rodolfo Giometti wrote:
> > Hello,
> >
> > here my implementation of Network Virtual terminals (NVT tty)
> > according to RFC 854 and RFC 2217... actually this is the client side
> > part since as remote server I used sredird
> > (http://freshmeat.net/projects/sredird/).
>
> Sounds interesting. Could you outline the limits a bit? In one of my use
> cases, I need to support 1200 baud with a rather esoteric 7E2 serial
> setup. (Needless to say, the client is a butt ugly win app to control
> gasoline pumps, running inself in a VMware WS setup. I'm supporting
> this since ten years now, where VMware took about 4 years to get the
> serial setup right finally...) Being able to redirect the serial data
> over network (in an inexpensive, but reliable way) would make my life
> significant easier in this respect.
My code is just one halve of the game... to solve your problem you
need a server on the machine where the serial port is installed and
you need that the server itself can manage it.
Here a simple schema of the whole game (it's my testing environment
but it can explain the situation anyway):
------------------+
+---------+ |
| minicom | |
+---------+ |
| | local PC with no
v | serial ports
/dev/nvtty0 |
| |
------------------+
|
v
/\/\/\/\/\
| network |
\/\/\/\/\/
|
------------------+
| |
v |
+---------+ |
| sredird | |
+---------+ | remote PC with
| | serial ports
v |
/dev/ttyS0 |
| |
------------------+
|
v
embedded PC with
a serial console
As you can see the program sredird
(http://freshmeat.net/projects/sredird/) manages the real serial port
according to the commands received from nvtty0 device and it
sends/receives the serial data to/from it and the userland application
(minicom in this example) doesn't see any difference from working on a
real serial port.
Hope this is useful to you.
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
Freelance ICT Italia - Consulente ICT Italia - www.consulenti-ict.it
prev parent reply other threads:[~2011-01-05 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 15:15 Network Virtual Terminal Rodolfo Giometti
2011-01-03 15:15 ` [PATCH] char nvtty: Network Virtual Terminal support Rodolfo Giometti
2011-01-03 17:14 ` Alan Cox
2011-01-03 18:02 ` Rodolfo Giometti
2011-01-03 18:22 ` Samuel Thibault
2011-01-03 23:32 ` Randy Dunlap
2011-01-05 14:48 ` Rodolfo Giometti
2011-01-04 17:13 ` Network Virtual Terminal Hans-Peter Jansen
2011-01-05 15:23 ` Rodolfo Giometti [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=20110105152313.GC3937@enneenne.com \
--to=giometti@enneenne.com \
--cc=gregkh@suse.de \
--cc=hpj@urpla.net \
--cc=linux-kernel@vger.kernel.org \
--cc=russell@coker.com.au \
/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