From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1G6Vaw-0004MT-9b
	for qemu-devel@nongnu.org; Fri, 28 Jul 2006 12:53:50 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1G6Vau-0004MC-4H
	for qemu-devel@nongnu.org; Fri, 28 Jul 2006 12:53:49 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1G6Vat-0004M9-Ur
	for qemu-devel@nongnu.org; Fri, 28 Jul 2006 12:53:47 -0400
Received: from [64.233.182.186] (helo=nf-out-0910.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1G6Vcv-0007Rs-Fe
	for qemu-devel@nongnu.org; Fri, 28 Jul 2006 12:55:53 -0400
Received: by nf-out-0910.google.com with SMTP id a25so226945nfc
	for <qemu-devel@nongnu.org>; Fri, 28 Jul 2006 09:53:46 -0700 (PDT)
Message-ID: <2ad73a0607280953u366ff2f3gb4a164ca2c94e2d3@mail.gmail.com>
Date: Fri, 28 Jul 2006 13:53:46 -0300
From: "=?ISO-8859-1?Q?Andr=E9_Braga?=" <meianoite@gmail.com>
Subject: Re: [Qemu-devel] How to Simulate hardware that counts scanlines?
In-Reply-To: <BAY114-F7583721F68BE69AE6A422BD580@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <BAY114-F7583721F68BE69AE6A422BD580@phx.gbl>
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

On 7/27/06, Steve Ellenoff <sellenoff@hotmail.com> wrote:
> The guest os code is polling this register on a very fast interval, and when
> it detects a certain # of scanlines have been counted, it will swap it's
> display buffers, ie, it's waiting for the vblank, so it can have nice smooth
> animations.

Since this is all custom, I'd rather raise an interrupt when the DAC
reaches the final portion of the frame buffer... This has to be better
than polling.