Here is the fix as you requested. But this begs the question, can our board specific files change at anytime? And not only be changed but be changed into something that does not work?
I can understand changing code in the rest of u-boot and having that break our board code, but I don't see the problem with our own board code using a depreciated method? Maybe just a note in our board code that a certain method is depreciated would be more appropriate? Is there another reason I am missing?
Matthew
On Thu, 2004-04-01 at 13:29, Wolfgang Denk wrote:
In message 1080835333.3255.47.camel@sabrina.arlut.utexas.edu you wrote:
Some files where changed in our board directory, I am not sure how or why they were changed. I do not see a mention of it in the changelog.
The relevant entry in the changelog is this:
Add a common get_ram_size() function and modify the the board-specific files to invoke that common implementation.
Attached is a patch correcting the problem, Wolfgang could you please apply it?
No, I will not. Please make your board use the common code instead.
Best regards,
Wolfgang Denk