projects / project / bcm63xx / u-boot.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 7ff8c7c) | patch
e6500: Move L1 enablement after L2 enablement
authorAndy Fleming <afleming@freescale.com>
Mon, 25 Mar 2013 07:33:14 +0000 (07:33 +0000)
committerAndy Fleming <afleming@freescale.com>
Tue, 14 May 2013 21:00:25 +0000 (16:00 -0500)
commit3e4c3137d6aefaf45a87bbad701fc336f3f24a3d
treec54a1d50c43176f8ff2ae429e4c8777780655459tree | snapshot
parent7ff8c7ce35c4468aac02f1ab4468e23384564eb0commit | diff
e6500: Move L1 enablement after L2 enablement

The L1 D-cache on e6500 is write-through. This means that it's not
considered a good idea to have the L1 up and running if the L2 is
disabled. We don't actually *use* the L1 until after the L2 is
brought up on e6500, so go ahead and move the L1 enablement after
that code is done.

Signed-off-by: Andy Fleming <afleming@freescale.com>
arch/powerpc/cpu/mpc85xx/start.S diff | blob | history
Broadcom-s U-Boot