From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FVy5M-00058t-Kp
	for qemu-devel@nongnu.org; Tue, 18 Apr 2006 17:50:12 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FVy5L-00058C-Nm
	for qemu-devel@nongnu.org; Tue, 18 Apr 2006 17:50:12 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FVy5L-000589-KY
	for qemu-devel@nongnu.org; Tue, 18 Apr 2006 17:50:11 -0400
Received: from [195.228.240.79] (helo=graveyard3.mail.t-online.hu)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FVy6J-0004TS-7N
	for qemu-devel@nongnu.org; Tue, 18 Apr 2006 17:51:11 -0400
Received: from mail.t-online.hu (karoly.axelero.hu [195.228.240.245])
	by graveyard3.mail.t-online.hu (Postfix) with ESMTP id BAA661F1AC9
	for <qemu-devel@nongnu.org>; Tue, 18 Apr 2006 23:50:08 +0200 (CEST)
Received: from mail.chello.hu (dsl51B676C0.pool.t-online.hu [81.182.118.192])
	by mail.t-online.hu (Postfix) with ESMTP
	for <qemu-devel@nongnu.org>; Tue, 18 Apr 2006 23:50:05 +0200 (CEST)
Date: Tue, 18 Apr 2006 23:50:04 +0200
From: NyOS <lista@nyos.homelinux.net>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-2
MIME-Version: 1.0
Message-ID: <op.s7739qe5t9pcbo@mail.chello.hu>
Content-Transfer-Encoding: quoted-printable
Subject: [Qemu-devel] bugreport -serial pipe:named_pipe_filename
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

Hi!

During developing a driver for a home-made serial hardware, I've noticed =
=20
that the 0 characters couldn't received in guest OS.

The HW is not ready yet, so I've bulit a test environment using Debian =20
GNU/Linux on Prescott (x86) as a host machine, and win98 as a guest. Qemu=
 =20
version is 0.8 release, (not the CVS one).

A bash script started the env.:

export QEMU_AUDIO_DRV=3Dalsa
nice -n 19 qemu -m 256 -soundhw sb16 -hda $HOME/image/qemu-win98.img =20
-localtime -net nic -net user -redir tcp:58000::58000 -redir =20
tcp:59000::59000 -serial pipe:/dev/qemuttyS0

/dev/qemuttyS* files are pipes, with read-write permission to the current=
 =20
user (tried other pipes also, in /home/nyos/...)

I've used 'cat' command to pipe test data to the named pipe (on the host)=
, =20
and the program (in guest) couldn't receive 0 bytes (0x00 hex code), but =
=20
it could any other one.
First I've thought it was my fault, but Hyperterm did the same.
Also tried sending through the same named pipe the same content, and it =20
was received correctly.

I've been using qemu for approx. half a year (0.7.2 earlier), and the sam=
e =20
image for several weeks, and it works, so I'm quite sure the problem is =20
somewhere in qemu code.
I'm not so familiar with its source, and after looking at serial.c, I =20
don't have an idea where the problem could be (maybe some string =20
manipulation because of '\0').

Could You have any idea what the problem is? (Or where should I look for =
=20
it.)

Nyos