From mboxrd@z Thu Jan 1 00:00:00 1970 From: Varun Wadekar Subject: Re: libfdt queries Date: Tue, 25 Oct 2011 12:38:24 +0530 Message-ID: <4EA66068.4020501@nvidia.com> References: <4EA6501B.3030907@nvidia.com> <20111025064723.GA5513@truffala.fritz.box> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111025064723.GA5513-MK4v0fQdeXQXU02nzanrWNbf9cGiqdzd@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: David Gibson Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org" List-Id: devicetree@vger.kernel.org > That seems a bit unlikely, but maybe. Is there any way you can dump > out the dtb after processing by your bootloader? > I will try to get a dump. > First thing would be to check if fdt_setprop_string() is returning an > error code. fdt_setprop_string() returns success. > Also, is that the only dtb manipulation you do, or do you make other > changes to the dtb? That's the only dtb manipulation I do. I tried hacking vprintk() to use early_printk() instead and I see that the kernel boots up. So it seems that only the "serial@xxxxxxxx" node contents are getting messed up. (Incidentally it also lies after the "chosen" node. I am just saying.) ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------