summaryrefslogtreecommitdiff
path: root/include/configs/M53017EVB.h
diff options
context:
space:
mode:
authorDavid Brownell <david-b@pacbell.net>2009-07-16 18:40:55 -0700
committerJean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>2009-08-03 09:26:26 +0200
commit06bffc6ea52d4b390843d295d438b2037d12e5fd (patch)
tree689ea76a23daa57493debfc4fbbf11984bab7271 /include/configs/M53017EVB.h
parent301b7db88fbdf7d118efb79b371b2527a2c31868 (diff)
downloadu-boot-imx-06bffc6ea52d4b390843d295d438b2037d12e5fd.zip
u-boot-imx-06bffc6ea52d4b390843d295d438b2037d12e5fd.tar.gz
u-boot-imx-06bffc6ea52d4b390843d295d438b2037d12e5fd.tar.bz2
rm9200 lowevel_init: don't touch reserved/readonly registers
For some reason the AT91rm9200 lowlevel init writes to a bunch of reserved or read-only addresses. All the boards seem to define the value-to-be-written values as zero ... but they shouldn't actually be writing *anything* there. No documented erratum justifies these accesses. It looks like maybe some pre-release BDI-2000 setup code has been carried along by cargo cult programming since at least late 2004 (per GIT history). Here's a patch disabling what seems to be bogosity. Tested on a csb337; there were no behavioral changes. Signed-off-by: David Brownell <david-b@pacbell.net> on RM9200ek Tested-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Diffstat (limited to 'include/configs/M53017EVB.h')
0 files changed, 0 insertions, 0 deletions