All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Pringlemeir <bpringlemeir@nbsps.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Attached DTB no longer supported u-boot.imx?
Date: Wed, 03 Dec 2014 10:43:59 -0500	[thread overview]
Message-ID: <87ppc0viv4.fsf@nbsps.com> (raw)
In-Reply-To: <20141129005753.GP20704@bill-the-cat> (Tom Rini's message of "Fri, 28 Nov 2014 19:57:53 -0500")


> On Fri, Nov 28, 2014 at 06:56:32PM -0500, Bill Pringlemeir wrote:

>> Sorry, both trees behave the same.  I will switch to separate
>> binaries.

On 28 Nov 2014, trini at ti.com wrote:

> This is not intentional.  I suspect I know what commit did this.  Can
> you please do a git bisect from v2015.01-rc1 to -rc2 and see what it
> says the bad commit is?  Thanks!

I have the 'ext4-div' patch and I must reduce the vf610 image size in
order to boot (why I have 'git reset --hard').

git reset --hard; git bisect bad
HEAD is now at c6150aa image-fdt: boot_get_fdt() return value when no DTB exists
c6150aaf2f2745141a7c2ceded58d7efbfeace7d is the first bad commit
commit c6150aaf2f2745141a7c2ceded58d7efbfeace7d
Author: Noam Camus <noamc@ezchip.com>
Date:   Wed Oct 22 17:17:49 2014 +0300

    image-fdt: boot_get_fdt() return value when no DTB exists
    
    I believe that when no DTB is around we should return 1.
    This why I fixed such scenarious to not return zero anymore.
    Else kernel might get NULL pointer to DTB which doesn't exists.
    
    Signed-off-by: Noam Camus <noamc@ezchip.com>

:040000 040000 f343f802d1491dc54545271694669c21f5efaa65 1120435d7aee7a9c12a6c8e2c0b19a364cbaf185 M      common

If I take rc2, revert c6150aaf2 and rebuild then the attached DTB image
seems fine for booting.

Regards,
Bill Pringlemeir.

  reply	other threads:[~2014-12-03 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 23:52 [U-Boot] Attached DTB no longer supported u-boot.imx? Bill Pringlemeir
2014-11-28 23:56 ` Bill Pringlemeir
2014-11-29  0:57   ` Tom Rini
2014-12-03 15:43     ` Bill Pringlemeir [this message]
2014-12-03 18:26       ` Tom Rini

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=87ppc0viv4.fsf@nbsps.com \
    --to=bpringlemeir@nbsps.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.