Hi Simon,
On Mon, Nov 12, 2018 at 9:58 PM Simon Glass sjg@chromium.org wrote:
Hi Bin,
On 11 November 2018 at 21:55, Bin Meng bmeng.cn@gmail.com wrote:
Hi Simon,
On Mon, Nov 12, 2018 at 11:25 AM Simon Glass sjg@chromium.org wrote:
Hi Bin,
On 7 November 2018 at 17:24, Bin Meng bmeng.cn@gmail.com wrote:
Hi Simon,
On Thu, Nov 8, 2018 at 1:09 AM Simon Glass sjg@chromium.org wrote:
On 7 November 2018 at 04:50, Bin Meng bmeng.cn@gmail.com wrote:
This reverts commit c0434407b595f785fc7401237896c48c791b45fd.
It turns out commit c0434407b595 broke some boards which have DM CPU driver with CONFIG_DISPLAY_CPUINFO option on. These boards just fail to boot when print_cpuinfo() is called during boot.
Fixes are already sent to ML and in u-boot-dm/next, however since we are getting close to the v2018.11 release, it's safer we revert the original commit.
This commit should be reverted after v2018.11 release.
Signed-off-by: Bin Meng bmeng.cn@gmail.com
common/board_f.c | 28 ---------------------------- include/init.h | 7 ------- 2 files changed, 35 deletions(-)
Thanks Bin. I'd like to get u-boot-dm/next set up ready for the merge window, so I presume in that we need to un-revert these changes and then pick up your two series?
That is correct. I can help test u-boot-dm/next.
OK thank you. It is ready there now.
Do you mean u-boot-dm/next? It looks to me the repo was updated 7 days ago.
Sorry u-boot-dm/testing. However I have pushed it to u-boot-dm/master now.
If you are sending new patches, can you please base on that?
Sure, I will take a look.
Regards, Bin