From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MfVku-0007MK-Uf for qemu-devel@nongnu.org; Mon, 24 Aug 2009 05:22:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MfVkp-0007FI-2Z for qemu-devel@nongnu.org; Mon, 24 Aug 2009 05:22:24 -0400 Received: from [199.232.76.173] (port=53219 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MfVko-0007Ew-He for qemu-devel@nongnu.org; Mon, 24 Aug 2009 05:22:18 -0400 Received: from mail2.shareable.org ([80.68.89.115]:43838) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MfVko-0006bI-8U for qemu-devel@nongnu.org; Mon, 24 Aug 2009 05:22:18 -0400 Date: Mon, 24 Aug 2009 10:22:14 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH 0 of 1] Fix for DOS keyboard problems Message-ID: <20090824092214.GA22972@shareable.org> References: <20090823124410.GA30789@shareable.org> <53e878390908231020s32575288jf2dd1450bae241c9@mail.gmail.com> <20090823215558.GA9093@shareable.org> <53e878390908231554o39fb1700n8b495e6c1089fc6@mail.gmail.com> <53e878390908240144v4c99fb89i7ac204356128d38f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53e878390908240144v4c99fb89i7ac204356128d38f@mail.gmail.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Ring Cc: qemu-devel@nongnu.org Stefan Ring wrote: > I will try to run C&C in Bochs, and I'm definitely not surprised that > my hack doesn't fix that as I'm almost 100% certain that it does its > own keyboard processing and bypasses the BIOS entirely (as virtually > all games do). On the other hand, I'd expect virtually all of the ones which handle the keyboard themselves (and disable the BIOS IRQ) to read port 0x60 exactly once per scan code. Which implies something else is broken too. Btw, a timer won't necessarily fix the problem seen with Borland, if QEMU/KVM are preempted at the wrong moment - unless there's a virtual CPU timer available which is not affected by host scheduling. -- Jamie