overo tide configured with incorrect clock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
x-loader (Ubuntu) |
Fix Released
|
Undecided
|
Ricardo Salveti |
Bug Description
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 24b8b7f41a83540
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>
Related branches
- X-Loader Packagers: Pending requested
-
Diff: 45 lines (+33/-0)2 files modifieddebian/patches/09-overo-Fix-bug-in-prcm_init.patch (+32/-0)
debian/patches/series (+1/-0)
tags: | added: armel |
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.