From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jdl.com (colo.jdl.com [66.118.10.122]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 8EFA967B1D for ; Tue, 20 Jun 2006 09:11:43 +1000 (EST) To: Segher Boessenkool Subject: Re: [PATCH 5/9 v3] Add the MPC8641 HPCN platform files. In-Reply-To: Your message of "Tue, 20 Jun 2006 00:44:35 +0200." References: <1150600056.23600.152.camel@localhost.localdomain> <1150725866.9022.5.camel@cashmere.sps.mot.com> Date: Mon, 19 Jun 2006 18:11:39 -0500 From: Jon Loeliger Message-Id: Cc: "linuxppc-dev@ozlabs.org" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , So, like, the other day Segher Boessenkool mumbled: > > In that case you obviously need to sync the timebases, sure. > The firmware could be smart and do the sync at CPU start-up > time though. I am investigating this and, as I indicated to Ben, submit a follow up patch to implement it if I figure out to do it. > In > some cases the kernel explicitly tells the firmware to start/ > stop the timebases, that's better than the kernel having to > handle the nitty-gritty details itself already. > > Thoughts? Well, by the time Linux is running, there is no more firmware available. Linux is essentially autononomous at this stage, and I think it will have to arrange for the TB sync itself. jdl