On Thu, Jun 07, 2018 at 10:29:53AM +0200, Pascal Vizeli wrote: > Thanks for this workaround. I will use this. > > I will later send a patch they store the device tree address on > raspberry into a variable. > So that user can load this, if he need it. > > The question is now, would you allow to load a device tree with a > memory address on oftree utility? > And if yes, where is the best place to add this function. Instead of a command I would prefer if you could just store r2 from the original bootloader you have been started with, and in a board specific initcall you copy the devicetree you found in memory to a file. Then the user has access to the devicetree with regular file commands and there is no need to guess the memory address where the original bootloader stored the device tree. 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
