From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bill Pringlemeir <bpringlemeir@nbsps.com>
Date: Fri, 28 Nov 2014 18:52:04 -0500
Subject: [U-Boot] Attached DTB no longer supported u-boot.imx?
Message-ID: <874mtiyjbv.fsf@nbsps.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


I tried to update the new u-boot I get,

  Bytes transferred = 3413041 (341431 hex)
  Kernel image @ 0x86000000 [ 0x000000 - 0x33e150 ]
  Could not find a valid device tree

The 'bootcmd' is,

 tftp ${loadaddr} zImage.dtb; bootz ${loadaddr}

has the syntax changed and I am not up to date?  I think I saw something
about an attached DTB not supported.

   u-boot-imx$ git describe
   v2009.08-18413-g5c84206

err, that is no good.  I have 2a82ec77d27ef5f860a107c4b764643a655dceeb
as 'Prepare v2015.01-rc2' and I had to apply 5c84206 to compile with a
4.9 hard-float ARM compiler.

I pulled the main 'u-boot.git' and this does not happen.

   u-boot$ git describe
   v2015.01-rc2-87-g0f89149

It is '38cd8c4253013ccdd4052ee021f6066fe9a52551', with the same patch as
'pwclient git-am 415336'

Is the imx just using newer patches to be merged to the main tree and I
must switch to a detached DT?  Or is there something else?

Thanks,
Bill.