linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Mikado <mikado4vn@gmail.com>
Cc: linux-c-programming@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Virtual Serial Port
Date: Sun, 26 Mar 2006 11:31:19 +0200 (MEST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0603261127580.22145@yvahk01.tjqt.qr> (raw)
In-Reply-To: <4425FB22.7040405@gmail.com>

>> You could write a device driver implementing virtual serial ports. Then you 
>> just add an ioctl that connects/disconnects virtual ports to real ports if 
>> desired.
>> I do not quite see what this would be good for, but I am sure it's 
>> good for learning or for fun. :)
>
>My purpose is to provide serial interfaces for debugging. My real box
>acts as remote host connecting to VMWare box by a *virtual* serial cable
>so that I can set up a debugging environment.
>
Ah! You don't want to have the X11 overhead of VMware. Quite an idea.
If I get it right, your setup looks like:

  guest writes to /dev/ttyS0
  vmware connects its virtual S0 to the host's ttyFakeS0
  minicom on the host to ttyFakeS0
or even
  vmware S0 to host's ttyS0
  other remote machine do minicom to ttyS0

The reason for FakeS0 is that vmware does not know about ptys, 
unfortunately.


Jan Engelhardt
-- 

  parent reply	other threads:[~2006-03-26  9:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-25 17:49 Virtual Serial Port Mikado
2006-03-25 18:47 ` Jan Engelhardt
2006-03-26  2:23   ` Mikado
2006-03-26  3:27     ` Anderson Lizardo
2006-03-26  9:31     ` Jan Engelhardt [this message]
2006-03-26 17:09       ` Mikado
2006-03-26 18:52         ` Petr Vandrovec
2006-03-27  3:29           ` Mikado
2006-03-26 16:07 ` Glynn Clements
2006-03-27 11:25 ` Holy Aavu
2006-03-27 17:29   ` Glynn Clements
2006-03-28  5:53     ` Holy Aavu

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=Pine.LNX.4.61.0603261127580.22145@yvahk01.tjqt.qr \
    --to=jengelh@linux01.gwdg.de \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikado4vn@gmail.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;
as well as URLs for NNTP newsgroup(s).