Hi, Wolfgang,
2011/4/22 Wolfgang Denk wd@denx.de:
Dear Jason Liu,
In message BANLkTi=Q7Ty4UtWWv5_3ED3gg3UeA3JiKQ@mail.gmail.com you wrote:
I think the only issue is if there is some reasons to set the test range to only 64KB, except the fact this was the value set for the mx51evk. If you do not see any special reasons, you could increase the CONFIG_SYS_MEMTEST_END to a larger value.
Is there any rule that we need must follow to set the CONFIG_SYS_MEMTEST_START CONFIG_SYS_MEMTEST_END ??
The only strict rule is that the test must work with the defined area.
Agree, I have tested it and it works.
If no, I think the value we set is free. Here I set for 64KB is just for simple and quick test, there is no other reasons.
In fact, mtest command line can override the value.
What the value you think I need set?
My recommendation is to set a range that is as big as possible for the given system, so the default call of the mtest command will actually test all (well, most of) the present RAM.
As I said, I just want the user to do one quick test for the memory. I don't think it need be set as big as possible.
Since there is no other rule I need follow for setting such value, So I will keep as it's.
Jason
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de On our campus the UNIX system has proved to be not only an effective software tool, but an agent of technical and social change within the University. - John Lions (U. of Toronto (?))