From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0.towertech.it (mx0.towertech.it [213.215.222.73]) by ozlabs.org (Postfix) with SMTP id 41908DDDFF for ; Thu, 6 Nov 2008 10:15:04 +1100 (EST) Date: Thu, 6 Nov 2008 00:14:59 +0100 From: Alessandro Zummo To: rtc-linux@googlegroups.com Subject: Re: [rtc-linux] Re: rtc-ppc Message-ID: <20081106001459.7eba302f@i1501.lan.towertech.it> In-Reply-To: <20081105230825.GA28465@yookeroo.seuss> References: <20081105021901.49dffc3e@i1501.lan.towertech.it> <1225923526.3882.3.camel@macbook.infradead.org> <20081105230825.GA28465@yookeroo.seuss> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: linuxppc-dev@ozlabs.org, David Woodhouse , david@gibson.dropbear.id.au List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 6 Nov 2008 10:08:25 +1100 David Gibson wrote: > > I think we're waiting until the RTC class works with NTP before we can > > contemplate that, though. > > Yeah, I tried writing some ppc_md hooks which backended onto the rtc > class drivers as an interim measure, but the hooks are called from > places the rtc class stuff can't safely be called (too early, IIRC, > but it's a while since I checked). I think the rtc drivers are too heterogeneous to have a valid ntp strategy. -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it