On Wed, Jun 6, 2018 at 8:16 AM, Pascal Vizeli <pvizeli@xxxxxxxxxx> 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. > > For implementation: > > Not sure what is the best. Maybe we can create a of_unflatten_file_dtb() and > of_unflatten_memory_dtb() they return fdt. There are a lot place they load > a fdt from a file and repeat the same code. > IMHO, an ideal solution to this problem would be to either extend RAMFS or create a separate FS that would allow mounting an arbitrary blob in RAM as a file with size determined using file_name_detect_type() + custom code or specified explicitly. That's quite a bit more work that this patch, though. Thanks, Andrey Smirnov _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
