From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HH2hv-0004jv-1a
	for qemu-devel@nongnu.org; Tue, 13 Feb 2007 13:48:51 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HH2hu-0004jU-MV
	for qemu-devel@nongnu.org; Tue, 13 Feb 2007 13:48:50 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HH2hu-0004jL-Hm
	for qemu-devel@nongnu.org; Tue, 13 Feb 2007 13:48:50 -0500
Received: from md2.t-2.net ([84.255.209.81])
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_3DES_EDE_CBC_SHA:24)
	(Exim 4.52) id 1HH2ht-0004tN-Uk
	for qemu-devel@nongnu.org; Tue, 13 Feb 2007 13:48:50 -0500
Message-ID: <45D2080B.1080401@kabelnet.net>
Date: Tue, 13 Feb 2007 19:48:43 +0100
From: =?ISO-8859-2?Q?Ale=B9_Rom?= <ales.rom@kabelnet.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit
Subject: [Qemu-devel] Serial port strange behavior
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Hello all . I'm new to this list.

A few days ago I asked on xen-users mailing list if xen and qemu serial 
driver code is related. Someone there confirmed that. After some digging 
and trying different serial port configurations I can say that  problem  
below is protocol related.
I hooked up two boxes with serial cable. First one is WinXP on real 
hardware, second one qemu (or xen) virtualized WinXP on FC6.
I started Hyper Terminal on both sides. Console communication is OK. 
Then I tried file transfer.

1. Real to virtual file transfer is good, other way not possible - using 
Zmodem protocol
2. Both ways file transfer is good - using Kermit protocol
If I try same thing on non virtual boxes, I don't have  this problem no 
matter what protocol I use.

The problem is that I can't change protocol when using proprietary 
application (for Win only) and this special device on COM port.
http://www2.sma.de/en/solar-technology/products/communication/communication-products-software/sunny-boy-control-plus/overview/index.html 

On the other way, emulated serial port is not acting the same as real 
one. Is this question for xen or qemu developers? Can I try anything else?

I can provide additional info if someone is interested, but I'm not a 
programmer to fix this problem :)

Thank you.

Aleš