From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1J2IAq-0000LM-Hi
	for qemu-devel@nongnu.org; Tue, 11 Dec 2007 22:22:16 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1J2IAl-0000KU-Vj
	for qemu-devel@nongnu.org; Tue, 11 Dec 2007 22:22:15 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1J2IAl-0000KR-RA
	for qemu-devel@nongnu.org; Tue, 11 Dec 2007 22:22:11 -0500
Received: from pop-gadwall.atl.sa.earthlink.net ([207.69.195.61])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <reif@earthlink.net>) id 1J2IAl-0002de-Tz
	for qemu-devel@nongnu.org; Tue, 11 Dec 2007 22:22:12 -0500
Received: from user-142h2k8.cable.mindspring.com ([72.40.138.136]
	helo=earthlink.net)
	by pop-gadwall.atl.sa.earthlink.net with esmtp (Exim 3.36 #1)
	id 1J2IAk-0000Hb-00
	for qemu-devel@nongnu.org; Tue, 11 Dec 2007 22:22:10 -0500
Message-ID: <475F5419.9030505@earthlink.net>
Date: Tue, 11 Dec 2007 22:23:05 -0500
From: Robert Reif <reif@earthlink.net>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] high resolution timer question
References: <475D3839.8040207@earthlink.net>	<f43fc5580712100951y152d48d9pe0df6eaed0d098a0@mail.gmail.com>	<475F333B.9040309@earthlink.net>
	<475F45BB.2010900@earthlink.net>
In-Reply-To: <475F45BB.2010900@earthlink.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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

Robert Reif wrote:

>> Characters written to serial port A are not reliably making it to the 
>> screen.
>> Turning on serial debugging shows that the characters are written to the
>> serial port.  The characters do make it to the screen when debugging.
>
>
> The problem seems to be caused by multiple streams outputting to the 
> screen.
> It looks like different ways of outputting to the same device may use 
> different
> streams!

Please disregard this possible cause.  I left a debugging printf in by 
accident.
The real problem is still there though.