From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Hquav-0004bq-JH
	for qemu-devel@nongnu.org; Wed, 23 May 2007 13:25:53 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Hquau-0004be-8i
	for qemu-devel@nongnu.org; Wed, 23 May 2007 13:25:53 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Hquau-0004ba-6K
	for qemu-devel@nongnu.org; Wed, 23 May 2007 13:25:52 -0400
Received: from sccrmhc11.comcast.net ([204.127.200.81])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <davis_g@comcast.net>) id 1Hquat-0004CZ-JK
	for qemu-devel@nongnu.org; Wed, 23 May 2007 13:25:51 -0400
Date: Wed, 23 May 2007 13:25:50 -0400
From: "George G. Davis" <davis_g@comcast.net>
Subject: Re: [Qemu-devel] Timers
Message-ID: <20070523172550.GE3110@mvista.com>
References: <200705230107.00962.paul@codesourcery.com>
	<f43fc5580705231000h36e03e1exb277bd9c219fbdf8@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f43fc5580705231000h36e03e1exb277bd9c219fbdf8@mail.gmail.com>
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 Wed, May 23, 2007 at 08:00:24PM +0300, Blue Swirl wrote:
> On 5/23/07, Paul Brook <paul@codesourcery.com> wrote:
> >I get fed up of having to re-implement a simple countdown timer for every 
> >new
> >board, so I've added a simple periodic timer implementation to cvs
> >(ptimer.c). Currently only the Arm PrimeCell based boards use this, but 
> >I've
> >a few other uses in the pipeline.
> 
> Nice idea! On Sparc the timer can be configured to work in 64-bit
> mode, so could the ptimer_get/set_count be changed to use 64-bit
> values?

Perhaps the width could be made runtime configurable, e.g. 16, 24, 32,
64-bits as required for a given system, since there are other targets
which may need differring widths (mind I haven't looked all too closely
at the code to see if it already handles this : ).  Likewise, perhaps
up/down count can also be made runtime configurable, since, again, some
targets implement up counters.  The logic is all the same in that
case, with just a difference in sign...
> 

-- 
Regards,
George

    _____   __o   George G. Davis - Software Engineer           (o>
-------    -\<,   MontaVista Sofware - Platform to Innovate     //\
 ------ ( )/ ( )  www.mvista.com                                V_/_
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~