On Wed, Dec 03, 2014 at 10:43:59AM -0500, Bill Pringlemeir wrote:
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@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.
Great, thanks!