Dear Benoit Monin,
In message 6148322.23690.1236356233840.JavaMail.www@wwinf8204 you wrote:
The configuration option is CONFIG_MFILL and this only takes effect if the memory commands are activated globally (CONFIG_CMD_MEM).
What exactly is the purpose of this patch? Looks like an extremely simple memory test to me. Don't we have already a rich selection of better ones available yet?
I should have detailed more the intent of those commands. We have here
Indeed.
a video controller embedded in an fpga with its own video ram. We use mfill to fill the video ram as fast as possible with variable data for each vram address. And we use mcheck to verify (as fast as possible) the content of the vram.
So this is not intended to test the main memory but it is a development and debug tool for peripheral containing memory.
You could use the existing memory tests to do the same.
I've sent a patch because they are useful to us and generic enough, and might be handy for debugging accesses to memory mapped behind programmable logic.
But maybe this debug tool is beyond the scope of U-Boot ?
I think it duplicates existing functionality.
Best regards,
Wolfgang Denk