devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Varun Wadekar <vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: libfdt queries
Date: Tue, 1 Nov 2011 09:47:08 +0530	[thread overview]
Message-ID: <4EAF72C4.5080503@nvidia.com> (raw)
In-Reply-To: <20111101005516.GD6895-MK4v0fQdeXQXU02nzanrWNbf9cGiqdzd@public.gmane.org>


>> 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.
> Ok.  You mean you were truncating the blob?

There is an internal function which actually copies the .dtb from a
partition on the eMMC to SDRAM before handing control to the kernel. I
forgot to set the proper size to be used after manipulating the command
line (since the command line size changed the copy routine should now
copy the updated size and should discard the old size).
>   Or you were manually
> (without libfdt) manipulating the size property somehow and messing
> that up?
>

libfdt was properly changing the size inside the blob, but I did not use
the updated size while copying the blob from eMMC to SDRAM.

-----------------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------------

      parent reply	other threads:[~2011-11-01  4:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25  5:58 libfdt queries Varun Wadekar
     [not found] ` <4EA6501B.3030907-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-10-25  6:47   ` David Gibson
     [not found]     ` <20111025064723.GA5513-MK4v0fQdeXQXU02nzanrWNbf9cGiqdzd@public.gmane.org>
2011-10-25  7:08       ` Varun Wadekar
2011-10-31 11:45       ` Varun Wadekar
     [not found]         ` <4EAE8A74.9020301-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-11-01  0:55           ` David Gibson
     [not found]             ` <20111101005516.GD6895-MK4v0fQdeXQXU02nzanrWNbf9cGiqdzd@public.gmane.org>
2011-11-01  4:17               ` Varun Wadekar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EAF72C4.5080503@nvidia.com \
    --to=vwadekar-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).