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>
Showing
- cpu/arm920t/at91rm9200/lowlevel_init.S 2 additions, 12 deletionscpu/arm920t/at91rm9200/lowlevel_init.S
- include/configs/at91rm9200dk.h 0 additions, 5 deletionsinclude/configs/at91rm9200dk.h
- include/configs/at91rm9200ek.h 0 additions, 5 deletionsinclude/configs/at91rm9200ek.h
- include/configs/cmc_pu2.h 0 additions, 5 deletionsinclude/configs/cmc_pu2.h
- include/configs/csb637.h 0 additions, 5 deletionsinclude/configs/csb637.h
- include/configs/m501sk.h 0 additions, 5 deletionsinclude/configs/m501sk.h
- include/configs/mp2usb.h 0 additions, 5 deletionsinclude/configs/mp2usb.h
Please register or sign in to comment