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. greets Pascal 2018-06-07 9:20 GMT+02:00 Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>: > On Wed, Jun 06, 2018 at 03:16:02PM +0000, Pascal Vizeli wrote: >> DON'T MERGE: this is only a concept patch. >> >> On some device, barebox is the second bootloader. The first bootloader provide >> some times allready a better device tree as the linux kernel own. >> Mostly barebox can't boot from this device tree but the linux kernel can. >> >> This patch allow to load a device tree from memory from first bootloader. > > Note while it may be handy to have a command for that, you can already > do this without writing code: > > memcpy -d /mydtb <dtbaddress> 0 0x10000 > oftree -l /mydtb > > The only drawback is that you have to guess the size of the dtb. > > 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
