overo tide configured with incorrect clock

[Andy Doan]

I noticed some errors in the Linaro dmesg log about incorrect clocking:

  Clocking rate (Crystal/Core/MPU): 26.0/224/500 MHz
  Reprogramming SDRC clock to 224791666 Hz
  dpll3_m2_clk rate change failed: -22

The current Overo x-loader is based on commit :
 2011-01-24: 7d0e587

Steve Sakoman added a fix a few days later that addresses this:

    commit 24b8b7f41a83540433024854736518876257672c
    Author: Steve Sakoman <email address hidden>
    Date: Sat Jan 29 00:52:29 2011 +0530

    overo: Fix bug in prcm_init

    The overo get_cpu_rev function was extended when 37XX support was
    added, but I neglected to modify the index calculation in prcm_init
    to compensate.

    Signed-off-by: Steve Sakoman <email address hidden>
    Tested-by: Philip Balister <email address hidden>
    Signed-off-by: Anand Gadiyar <email address hidden>

[Andy Doan (doanac)]

I have the fix in my git repo. I'll convert it over to the BZR project and do a merge proposal as soon as I get a chance.

[Ricardo Salveti (rsalveti)]

Branch merged at lp:x-loader. Jani or Loic, can you help me sponsoring the package to fix this bug?

I'm planning another x-loader update, to fix some other issues, but would be good to have this fixed now.

[Launchpad Janitor (janitor)]

This bug was fixed in the package x-loader - 1.4.4+git20110124+7d0e587-1ubuntu1

---------------
x-loader (1.4.4+git20110124+7d0e587-1ubuntu1) natty; urgency=low

  [ Andy Doan ]
  * debian/patches/09-overo-Fix-bug-in-prcm_init.patch:
    - Fix bug in prcm_init at Overo (LP: #737280)
 -- Ricardo Salveti de Araujo <email address hidden> Fri, 18 Mar 2011 01:38:53 -0300