In message 200804211145.28004.sr@denx.de you wrote:
Well, it affects only processors which need MMU support. Most doen't.
I'm not so sure here anymore with all the newer PPC's and other platforms. But I have to admit that I'm no expert for those other platforms.
It's only processors which run in 32 bit mode but are capable of addressing > 32 bit physical address space.
Another problemtic issue could be the POST area for caches etc. I know that self modifying code is used here in some places. This could be more problematic with caches enabled.
The POST code is supposed to take care of that.
Next release means the one that comes after the next merge window.
I did understand this part of the sentence. I'm just not sure what should happen with the current code if it doesn't get changed. Again, I personally can't promise to "fix" this issue until the next merge window opens.
If you fix it "until the next merge window opens", it will come in time for the next release, so we all are happy.
For now (i. e. for the upcoming 1.3.3 release), let's use this quick and really dirty hack to silence the 440 build errors.
Best regards,
Wolfgang Denk