From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I6pPc-0003Ib-Vv for qemu-devel@nongnu.org; Fri, 06 Jul 2007 11:08:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I6pPc-0003IK-KP for qemu-devel@nongnu.org; Fri, 06 Jul 2007 11:08:00 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I6pPc-0003IG-Bi for qemu-devel@nongnu.org; Fri, 06 Jul 2007 11:08:00 -0400 Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5] helo=grelber.thyrsus.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I6pPb-0001Zc-W0 for qemu-devel@nongnu.org; Fri, 06 Jul 2007 11:08:00 -0400 Received: from landley.net (localhost [127.0.0.1]) by grelber.thyrsus.com (Postfix) with ESMTP id 21F15738DE for ; Fri, 6 Jul 2007 11:09:08 -0400 (EDT) From: Rob Landley Date: Fri, 6 Jul 2007 11:07:57 -0400 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200707061107.57639.rob@landley.net> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Persistent clock on arm target? 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 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... Right now I'm running rdate from my init scripts to work around this... Rob -- "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson.