ARM's multiply-mapped memory mess

This puzzles me too. I guessed as marcH does, in the first answer to your question. It sure sounds spooky, but if it's been running this way for some time (years?), it must be one of those things that the manufacturer might want to use themselves someday for something different, so they put out a vague "undefined" warning while knowing that it does work.