From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I6pae-00035Q-5m for qemu-devel@nongnu.org; Fri, 06 Jul 2007 11:19:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I6pac-00034R-NY for qemu-devel@nongnu.org; Fri, 06 Jul 2007 11:19:23 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I6pac-00034I-Fz for qemu-devel@nongnu.org; Fri, 06 Jul 2007 11:19:22 -0400 Received: from ug-out-1314.google.com ([66.249.92.175]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I6pab-000541-4a for qemu-devel@nongnu.org; Fri, 06 Jul 2007 11:19:21 -0400 Received: by ug-out-1314.google.com with SMTP id m2so692786uge for ; Fri, 06 Jul 2007 08:19:10 -0700 (PDT) Message-ID: Date: Fri, 6 Jul 2007 17:19:10 +0200 From: "andrzej zaborowski" Subject: Re: [Qemu-devel] Persistent clock on arm target? In-Reply-To: <200707061107.57639.rob@landley.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200707061107.57639.rob@landley.net> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 06/07/07, Rob Landley wrote: > Is there any way to get a persistent clock into an arm versatilepb target so > the clock doesn't start initialized to January 1, 1970? (Do I have to enable > some Linux kernel driver to find this hardware?) > > On irc paul brook said it was "fixed in CVS a few days ago", but I just > updated to last night's snapshot and there was no difference. I don't really > know what I'm looking for, actually... There's a kernel patch for pl031 in the message I linked in my last message. Andrew