Hi, Stefano,
2011/4/22 Stefano Babic sbabic@denx.de:
On 04/22/2011 06:36 AM, Jason Hui wrote:
OK, I will resend the patchset as the following layout:
MX5: clock: Add clock config interface MX5: factor out boot cause funciton to common code PMIC: Add dialog pmic support MX53: support for freescale MX53LOCO board (merge "Add power init support")
I will rebase on the u-boot-imx git, do you think is it OK?
Yes, thanks.
+#define CONFIG_SYS_MEMTEST_START 0x70000000 +#define CONFIG_SYS_MEMTEST_END 0x70010000
There is still an open question about this range. Can you answer to Wolfgang's question ?
In fact, I want to give one simple test range when use mtest, I don't know what you are worrying about, please tell it clearly?
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 ??
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?
Jason
Best regards, Stefano
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de ===================================================================== _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot