From mboxrd@z Thu Jan  1 00:00:00 1970
From: Timur Tabi <timur@freescale.com>
Date: Mon, 10 Dec 2007 13:04:09 -0600
Subject: [U-Boot-Users] What do I do if
	fdt_setprop()	returns	-FDT_ERR_NOSPACE?
In-Reply-To: <475A0509.8040703@freescale.com>
References: <4759BB15.9000006@freescale.com> <4759BE83.7000402@ge.com>
	<475A0509.8040703@freescale.com>
Message-ID: <475D8DA9.4010408@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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