Hi Tom, Michal,
2015-04-09 2:59 GMT+09:00 Michal Simek michal.simek@xilinx.com:
On 04/08/2015 04:04 PM, Tom Rini wrote:
On Wed, Apr 08, 2015 at 10:03:28AM +0200, Michal Simek wrote:
On 04/08/2015 07:25 AM, Masahiro Yamada wrote:
Since commit 326a682358c1 (malloc_f: enable SYS_MALLOC_F by default if DM is on), Zynq MMC boot hangs up after printing the following:
U-Boot SPL 2015.04-rc5-00053-gadcc570 (Apr 08 2015 - 12:59:11) mmc boot reading system.dtbPrior to commit 326a682358c1, Zynq boards enabled CONFIG_DM, but not CONFIG_SYS_MALLOC_F. That commit forcibly turned on CONFIG_SYS_MALLOC_F. I have not figured out the root cause, but anyway it looks like CONFIG_SYS_MALLOC_F gave a bad impact on the Zynq MMC boot.
We are planning to have the v2015.04 release in a few days. I know this is a defensive fixup, but what I can do now is to add # CONFIG_SYS_MALLOC_F is not set to every Zynq defconfig file to get back the original behavior.
Tested on:
- Zedboard
- ZC706 board
Signed-off-by: Masahiro Yamada yamada.masahiro@socionext.com Cc: Michal Simek michal.simek@xilinx.com Cc: Simon Glass sjg@chromium.org
This problem is urgent!
If we cannot find the better solution, please apply this patch by the v2015.04 release. ^^^^^^^^^^^^^^^^^^^^^^^
Tested-by: Michal Simek michal.simek@xilinx.com
Tom: Can you please add it to your tree?
Do you want to do a PR with this (or wait a bit for Simon and Masahiro to root-cause) and your maintainers update or should I just grab that directly too? Thanks!
Please grab both patches directly to your tree. When Simon or Masahiro find out root cause then we can simple revert it. This seems to be the best strategy for now.
I agree.