From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bin Meng Date: Wed, 26 Sep 2018 14:40:55 +0800 Subject: [U-Boot] [PATCH 4/4] Revert "x86: galileo: Fix boot failure" In-Reply-To: References: <20180902230227.26643-1-sjg@chromium.org> <20180902230227.26643-5-sjg@chromium.org> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Simon, On Wed, Sep 26, 2018 at 1:42 PM Simon Glass wrote: > > Hi Bin, > > On 4 September 2018 at 03:07, Bin Meng wrote: > > Hi Simon, > > > > On Mon, Sep 3, 2018 at 7:02 AM Simon Glass wrote: > >> > >> The root cause of this problem should now be fixed. Renable bootstage. > >> > >> (Note, if this does not fix it, and instead a -ENOMEM error is produced, > >> then we probably need to increase CONFIG_SYS_MALLOC_F_LEN a bit). > >> > >> This reverts commit 7995dd3782f90e1939969a4ead800a5e98e2d197. > >> > >> Signed-off-by: Simon Glass > >> --- > >> > >> configs/galileo_defconfig | 3 +++ > >> 1 file changed, 3 insertions(+) > >> > > > > I think this breaks Galileo, though I do not have a board to test right now. > > > > If you look at galileo.dts, it explicitly describes TSC frequency in > > the DT, but current TSC timer early support codes does not support > > reading TSC frequency in the DT. Maybe we need a config option for > > such hardware that can't calibrate TSC frequency? > > Yes we could. Until then perhaps we can park this patch. Thanks. Then I will apply patch 2 and 3 in this series. Regards, Bin