From: Michael Buesch <freesoftwaredeveloper@web.de>
To: Jeff Randall <randall@uph.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Serial port over TCP/IP
Date: Sun, 6 Apr 2003 23:30:47 +0200 [thread overview]
Message-ID: <200304062330.47814.freesoftwaredeveloper@web.de> (raw)
In-Reply-To: <20030406161206.A12616@uph.com>
On Sunday 06 April 2003 23:12, Jeff Randall wrote:
> On Sun, Apr 06, 2003 at 10:47:45PM +0200, Michael Buesch wrote:
> > On Sunday 06 April 2003 22:14, Jeff Randall wrote:
> > > Yes, it would be very possible to do.
> >
> > Yes, but after Rob posted this script
> >[...]
> > do you think it's still neccessary to develop a driver?
> > I don't think so.
>
> Depends what kind of flexiblity you want. If you have no need to support
> IOCTL's remotely, that script is probably sufficient.
Hm, that's the point. I don't know if ioctls are needed, because I'm not the
user of this "network COM-port", but only the possible developer. :)
I'll ask the person, who requested this feature tomorrow.
I think ioctls might be needed for his application. But the simple
nc-script doesn't provide them.
One thing is clear: For server-side there is no need for kernel-support.
But for the client kernel-support might be the best solution.
Regards Michael Buesch.
--
My homepage: http://www.8ung.at/tuxsoft
fighting for peace is like fu**ing for virginity
next prev parent reply other threads:[~2003-04-06 21:19 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 [this message]
2003-04-07 2:37 ` H. Peter Anvin
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=200304062330.47814.freesoftwaredeveloper@web.de \
--to=freesoftwaredeveloper@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randall@uph.com \
/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