+ ocotea-board-ntpd-complains-that-the-frequency-error-exceeds-the-tolerance.patch added to -mm tree

[Kumar Gala]

On Mar 16, 2007, at 5:52 AM, akpm at linux-foundation.org wrote:

>
> The patch titled
>      Ocotea board: ntpd complains that the frequency error exceeds  
> the tolerance
> has been added to the -mm tree.  Its filename is
>      ocotea-board-ntpd-complains-that-the-frequency-error-exceeds- 
> the-tolerance.patch
>
> *** Remember to use Documentation/SubmitChecklist when testing your  
> code ***
>
> See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt  
> to find
> out what to do about this
>
> ------------------------------------------------------
> Subject: Ocotea board: ntpd complains that the frequency error  
> exceeds the tolerance
> From: Bart Van Assche <bart.vanassche at gmail.com>
>
> Lifted from http://bugzilla.kernel.org/show_bug.cgi?id=8182
>
> Steps to reproduce:
> - Boot an Ocotea board with the mainline 2.6.20.1 kernel.
> - Create an /etc/ntp.conf file with at least one NTP server and  
> iburst mode set.
> - Issue the command "ntpd -g".
> - Wait about two minutes.
> - Verify ntpd's status via "ntpq -pn" and by looking in /var/log/ntp.
>
> Patch that fixes this problem:
>
> Cc: Kumar Gala <galak at gate.crashing.org>
> Cc: Benjamin Herrenschmidt <benh at kernel.crashing.org>
> Cc: Paul Mackerras <paulus at samba.org>
> Signed-off-by: Andrew Morton <akpm at linux-foundation.org>
> ---
>
>  arch/ppc/platforms/4xx/ocotea.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -puN arch/ppc/platforms/4xx/ocotea.c~ocotea-board-ntpd- 
> complains-that-the-frequency-error-exceeds-the-tolerance arch/ppc/ 
> platforms/4xx/ocotea.c
> --- a/arch/ppc/platforms/4xx/ocotea.c~ocotea-board-ntpd-complains- 
> that-the-frequency-error-exceeds-the-tolerance
> +++ a/arch/ppc/platforms/4xx/ocotea.c
> @@ -289,7 +289,7 @@ ocotea_setup_arch(void)
>  	 * from FPGA, because it can be changed by on-board switches
>  	 * --ebs
>  	 */
> -	ibm440gx_get_clocks(&clocks, 33333333, 6 * 1843200);
> +	ibm440gx_get_clocks(&clocks, 33300000, 6 * 1843200);
>  	ocp_sys_info.opb_bus_freq = clocks.opb;

  I asked Stefan & Josh to look at this and Stefan believes its a  
33.33Mhz clock.  So should this really be 33330000?

- k

>
>  	/* Setup TODC access */
> _
>
> Patches currently in -mm which might be from  
> bart.vanassche at gmail.com are
>
> ocotea-board-ntpd-complains-that-the-frequency-error-exceeds-the- 
> tolerance.patch