From: Mikado <mikado4vn@gmail.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Glynn Clements <glynn@gclements.plus.com>
Cc: linux-kernel@vger.kernel.org, linux-c-programming@vger.kernel.org
Subject: Re: Virtual Serial Port
Date: Mon, 27 Mar 2006 00:09:51 +0700 [thread overview]
Message-ID: <4426CADF.2050902@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603261127580.22145@yvahk01.tjqt.qr>
-----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]
But today I've just bought an USB-to-Serial converter and made for
myself a null-modem serial cable. I use this null-modem cable to connect
/dev/ttyS0 (native serial port) to /dev/tts/USB0 (USB-based serial
port). My VMWare now can use one of those devices and the host use
another one. Now above figure can be re-drawn like this:
[host - application] <- read/write -> [/dev/tts/USB0] <- read/write over
physical null-modem cable -> [/dev/ttyS0] <- read/write -> [VMWare -
application]
Anyway, later I'll try to write a device drivers act as virtual serial
ports and virtual null-modem cables.
Best regards,
Mikado.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEJsrfNWc9T2Wr2JcRAl05AJ9Ee8zqagf0yjDk71mFAxwSskFltQCg0aM8
mELZ8uxHPaSYzLiZLM7Cxy4=
=zI/+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-03-26 17:09 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 [this message]
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=4426CADF.2050902@gmail.com \
--to=mikado4vn@gmail.com \
--cc=glynn@gclements.plus.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-c-programming@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).