[U-Boot] [PATCH] cmd_mem: Decode the mtest start and end values from fdt

[Wolfgang Denk <wd@denx.de>]

Dear Jagannadha Sutradharudu Teki,

In message <ff1257d2-b332-477f-915d-0851e5ef944f@CO9EHSMHS030.ehs.local> you wrote:
>
> I think the entire change are not good as it touches the environment concept,
> Can you suggest any better way we could do or it may not be possible/require the mem test values
> alter though devicetree.

May I ask _why_ you would want to do this in the first place?

It does not seem to make sense to me.

Please also note that "mtest" is basicly useless.  Totally useless,
to be honest.  It performs plain read / write cycles, and unless you
have very basic memory issues this will always work - if you have
such, these get detected when running get_ram_size().

"mtest" was once added as an explicit requirement of a customer to
meet some formal specification requests. It is a ZERO practical use.

If you want to do memory testing, then use the memory test functions
of the POST framework.  OK, these will not exercise any burst mode
accesses either, but they are at least a bit more useful.

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 at denx.de
The evolution of the human race will not be accomplished in  the  ten
thousand  years  of  tame  animals,  but in the million years of wild
animals, because man is and will always be a wild animal.
                                              - Charles Galton Darwin