From mboxrd@z Thu Jan 1 00:00:00 1970 From: Varun Wadekar Subject: Re: libfdt queries Date: Mon, 31 Oct 2011 17:15:56 +0530 Message-ID: <4EAE8A74.9020301@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? > Found out the root cause. My bootloader was not manipulating the dtb blob size properly and hence the final dtb was messed up. This resulted in the kernel not finding proper fields inside the dtb. Sorry for the false alarm. Issue closed. ----------------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------------