[U-Boot] [STATUS] v2010.12-rc2 released

Ben Gardiner bengardiner at nanometrics.ca
Tue Nov 30 20:50:36 CET 2010


On Tue, Nov 30, 2010 at 10:00 AM, Wolfgang Denk <wd at denx.de> wrote:
> Hello everybody.
>
> I apologise for being a bit late with this announcement:
>
> * U-Boot v2010.12-rc2 was released on Sunday, November 28.
>
> * Release "v2010.12" is (still) scheduled in 13 days:
>  on December 13, 2010.
>
> Please help testing, and check if all your relevant patches have been
> included.

da850evm was broken by

commit 4f6fc15b42776b12244af8aa28da42c8e6497742
Author: Sekhar Nori <nsekhar at ti.com>
Date:   Fri Nov 19 11:39:48 2010 -0500

    DA850 EVM: passing maximum clock rate information to kernel

    The TI DA850/OMAP-L138/AM18x EVM can be populated with devices
    having different maximum allowed CPU clock rating.

    The maximum clock the chip can support can only be determined from
    the label on the package (not software readable).

    Introduce a method to pass the maximum allowed clock rate information
    to kernel using ATAG_REVISION. The kernel uses this information to
    determine the maximum cpu clock rate reachable using cpufreq.

    Note that U-Boot itself does not set the CPU clock rate. The CPU
    clock is setup by a primary bootloader ("UBL"). The rate setup by
    UBL could be different from the maximum clock rate supported by the
    device.

    Signed-off-by: Sekhar Nori <nsekhar at ti.com>
    Signed-off-by: Sandeep Paulraj <s-paulraj at ti.com>

With the introduction of this patch the board freezes after UBL jumps
to 0xC1080000; however, I don't think it was the implementation in
this patch that caused the breakage.

Removing the added "#define CONFIG_REVISION_TAG" does not fix the
freeze. Furthermore, reverting the patch on top of 2010.12-rc2 does
not fix the freeze either. Finally to add to the (/my) confusion,
adding OPTFLAGS="-O0 -g" to 4f6fc15b42776b12244af8aa28da42c8e6497742^
(the commit parent) results in a boot freeze, where there was none
before the addition of the compiler flags.

I suppose we should be suspecting the timers? I think I recall hearing
that the time code can mix poorly with relocation.

Best Regards,
Ben Gardiner

---
Nanometrics Inc.
http://www.nanometrics.ca


More information about the U-Boot mailing list