From: "Kazu" <kazoo@r3.dion.ne.jp>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Serial port suppourt for win32
Date: Wed, 15 Mar 2006 15:44:42 +0900 [thread overview]
Message-ID: <002701c647fb$f0e63560$0464a8c0@athlon> (raw)
Hi,
It is an experimental serial port support for win32. Here is patches and a
binary.
http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060311-serial-3.patch
http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060311-16550a.patch
http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060311-serial-win2kxp.patch
http://www.h6.dion.ne.jp/~kazuw/qemu-win/qemu-20060311-serial.zip
The 16550A patch is by Benoit Canet from here.
http://lists.gnu.org/archive/html/qemu-devel/2006-02/msg00004.html
An option is:
-serial COM1
Use upper-case for COM number.
Dialog is popped up and set communication parameters.
After patches are applied and the first time Windows boots, Windows
recognizes the device is updated. So wait until a device driver is installed
and reboot.
I have not tested a real COM port.
I used ComEmulDrv which provides a virtual COM port pair as a device driver
for Win2k/XP. I set COM5 and COM6 by it and used HyperTerminal on both Win2k
guest and WinXP host. Files can be transfer between them.
http://mixw.net/related.htm#tncemu
Communication parameters are important. Tested parameters are:
Baud rate: 9600 bps
Data bit: 8 bit
Parity: none
Stop bit: 1
Flow control: none
It is necessary to set the same parameters among the guest and the host
and QEMU.
When flow control is hardware, if qemu-20060311-serial-win2kxp.patch is not
used, data can not be sent from Win2k guest to WinXP host.
It is too slow to use windbg. I will try to make a patch to use a named pipe
for it.
Regards,
Kazu
next reply other threads:[~2006-03-15 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 6:44 Kazu [this message]
2006-03-27 7:00 ` [Qemu-devel] [PATCH] Serial port suppourt for win32 Kazu
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='002701c647fb$f0e63560$0464a8c0@athlon' \
--to=kazoo@r3.dion.ne.jp \
--cc=qemu-devel@nongnu.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).