
30 Nov
2015
30 Nov
'15
6:41 a.m.
On Sunday 29 November 2015 10:46 AM, Simon Glass wrote:
At present bootstage will try to read the timer very early after relocation. When driver model it used to provide the timer, we cannot read it until driver model is ready. Correct this by adding a separate stage for the post-relocation bootstage init.
This fixes booting on chromebook_link.
Signed-off-by: Simon Glass sjg@chromium.org
Reviewed-by: Mugunthan V N mugunthanvnm@ti.com
Regards Mugunthan V N