public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Serial port over TCP/IP
Date: 6 Apr 2003 19:37:57 -0700	[thread overview]
Message-ID: <b6qoa5$edn$1@cesium.transmeta.com> (raw)
In-Reply-To: 200304061447.46393.freesoftwaredeveloper@web.de

Followup to:  <200304061447.46393.freesoftwaredeveloper@web.de>
By author:    Michael Buesch <freesoftwaredeveloper@web.de>
In newsgroup: linux.dev.kernel
> 
> Is it possible to make a char-dev (a serial device ttyS0)
> available via TCP/IP on a network like it is possible
> for block-devices like a harddisk via nbd?
> Is kernel-support for this present?
> If not, is it technically possible to develop such a driver?
> 

I think what you need is the enhanced pty driver patch which was
posted recently, which made is possible for a user-space process to
also capture ioctls() such as baud rate setting etc.  Then the rest of
the work can be done in userspace.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64

  parent reply	other threads:[~2003-04-07  2:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06 12:47 Serial port over TCP/IP Michael Buesch
2003-04-06 13:11 ` Dr. David Alan Gilbert
2003-04-06 13:39   ` Michael Buesch
2003-04-06 13:46     ` Dr. David Alan Gilbert
2003-04-06 13:35 ` Rob van Nieuwkerk
2003-04-06 13:41   ` Michael Buesch
     [not found] ` <200304062247.45525.freesoftwaredeveloper@web.de>
     [not found]   ` <20030406161206.A12616@uph.com>
2003-04-06 21:30     ` Michael Buesch
2003-04-07  2:37 ` H. Peter Anvin [this message]
2003-04-07 14:53   ` Michael Buesch

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='b6qoa5$edn$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@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