Hi Andrey, On Wed, May 13, 2015 at 07:54:27PM -0700, Andrey Smirnov wrote: > Add an option to perform DRAM region validation before using it. The > framework allows individual boards to set up a memory validaion hook > that would be called prior to Barebox using that region of memory. > > Signed-off-by: Andrey Smirnov <andrew.smirnov@xxxxxxxxx> What usecase do you have for this patch? Is it debugging or something you always want to enable on your hardware? Why must the validate_memory_range function be board specific? I see that you call validate_memory_range on potentially large areas of memory, so I wonder if you can't call validate_memory_range from your board setup code with the complete memory instead. I am not very fond of overly using get_runtime_offset to calculate pointers. Setting callback functions from early code which does not run on its link address is something I really want to avoid. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
