linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: mikado4vn@gmail.com
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Glynn Clements <glynn@gclements.plus.com>,
	linux-kernel@vger.kernel.org,
	linux-c-programming@vger.kernel.org
Subject: Re: Virtual Serial Port
Date: Sun, 26 Mar 2006 20:52:51 +0200	[thread overview]
Message-ID: <4426E303.9000701@vc.cvut.cz> (raw)
In-Reply-To: <4426CADF.2050902@gmail.com>

Mikado wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
>>  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.
> 
> 
> Yes, VMWare doesn't support serial port using host's ttys any more. My
> idea is:
> 
> [host - application] <- read/write -> [virtual serial port
> /dev/ttyFakeS0] <- read/write over virtual null-modem serial cable ->
> [host - real serial port /dev/ttyS0] <- read/write -> [VMWare - application]

Although it is quite irrelevant to LKML (you may want to visit 
www.vmware.com/community/index.jspa and ask there...), you can connect guest's 
serial port also to Unix socket - and in such situation you need virtual serial 
port driver only if 'host - application' does not know how to use /dev/tty* (for 
unix socket <-> /dev/ptyp* app look at 
http://platan.vc.cvut.cz/ftp/pub/vmware/serpipe.tar.gz).
								Petr


  reply	other threads:[~2006-03-26 18:52 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
2006-03-26 17:09       ` Mikado
2006-03-26 18:52         ` Petr Vandrovec [this message]
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=4426E303.9000701@vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=glynn@gclements.plus.com \
    --cc=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).