[U-Boot-Users] What do I do if fdt_setprop() returns -FDT_ERR_NOSPACE?

[Timur Tabi]

Timur Tabi wrote:
> Jerry Van Baren wrote:
> 
>> I would try 0x4000 and see if it works. :-)
> 
> I increased it to 0x8000 and it still didn't work. 

Ok, it turns out this is another symptom of the relocation bug.  If I call 
fdt_set_qe_firmware() directly instead of via a function pointer, everything 
works.  I guess I need to find a work-around.

-- 
Timur Tabi
Linux kernel developer at Freescale