74xx: use r4 instead of r2 in lock_ram_in_cache and unlock_ram_in_cache
authorDave Liu <daveliu@freescale.com>
Thu, 23 Oct 2008 13:59:35 +0000 (21:59 +0800)
committerWolfgang Denk <wd@denx.de>
Thu, 30 Oct 2008 23:25:08 +0000 (00:25 +0100)
commitd685b74c64a38849f1a129b3ab846fbf67dd937e
tree5d54e7ffb276dc281d2b59af70f521c8810b302a
parentd344293a5b953eff1c8617e6b89703e82f7ca13f
74xx: use r4 instead of r2 in lock_ram_in_cache and unlock_ram_in_cache

The patch is following the commit 392438406041415fe64ab8748ec5ab5ad01d1cf7

mpc86xx: use r4 instead of r2 in lock_ram_in_cache and unlock_ram_in_cache

This is needed in unlock_ram_in_cache() because it is called from C and
will corrupt the small data area anchor that is kept in R2.

lock_ram_in_cache() is modified similarly as good coding practice, but
is not called from C.

Signed-off-by: Nick Spence <nick.spence@freescale.com>
also, the r2 is used as global data pointer.

Signed-off-by: Dave Liu <daveliu@freescale.com>
cpu/74xx_7xx/start.S