All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Bob Burke <Bob.Burke@terascala.com>
Subject: Re: [PATCH] PowerPC 440EPx: Sequoia bootwrapper
Date: Tue, 21 Jul 2009 16:06:52 +0200	[thread overview]
Message-ID: <200907211606.52572.sr@denx.de> (raw)
In-Reply-To: <2C7DE72B9BD00F44BAECA5B0CBB873956CDC2B@hermes.terascala.com>

On Tuesday 21 July 2009 15:33:20 Bob Burke wrote:
> The system clock frequency on the Sequoia board is 33.000000 MHz not
> 33.333333 MHz; this causes the system time to drift more than 30 seconds
> per hour.
>
> diff -ruN a/arch/powerpc/boot/cuboot-sequoia.c
> b/arch/powerpc/boot/cuboot-sequoia.c
> --- a/arch/powerpc/boot/cuboot-sequoia.c        2009-05-18
> 19:52:34.000000000 -0400
> +++ b/arch/powerpc/boot/cuboot-sequoia.c        2009-07-21
> 09:13:13.000000000 -0400
> @@ -37,7 +37,7 @@
>
>  static void sequoia_fixups(void)
>  {
> -       unsigned long sysclk = 33333333;
> +       unsigned long sysclk = 33000000;
>
>         ibm440ep_fixup_clocks(sysclk, 11059200, 50000000);
>         ibm4xx_fixup_ebc_ranges("/plb/opb/ebc");

Unfortunately it's not that easy. Earlier Sequoia board revisions are equipped 
with an 33.333MHz oscillator. This can be detected via a CPLD register though. 
Here the "code" from U-Boot (just as an example):

/* Detect Sequoia PLL input clock automatically via CPLD bit            */
#define CONFIG_SYS_BCSR_BASE            0xc0000000
#define CONFIG_SYS_CLK_FREQ    ((in8(CONFIG_SYS_BCSR_BASE + 3) & 0x80) ? \
                                33333333 : 33000000)

But why are you using the boot wrapper? If your U-Boot isn't too old, you can 
boot uImage directly (with dtb of course). No need for the wrapper.

Thanks,
Stefan

  reply	other threads:[~2009-07-21 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 13:33 [PATCH] PowerPC 440EPx: Sequoia bootwrapper Bob Burke
2009-07-21 14:06 ` Stefan Roese [this message]
2009-07-21 15:56   ` Bob Burke
2009-07-21 16:52     ` Stefan Roese

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200907211606.52572.sr@denx.de \
    --to=sr@denx.de \
    --cc=Bob.Burke@terascala.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.