From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Thu, 21 Mar 2013 10:41:45 -0400 Subject: [U-Boot] [PATCH] Fix bootdelay timeout calculation when SYS_HZ!=1000 In-Reply-To: <20130321143540.B01CF200547@gemini.denx.de> References: <1363842874-8286-1-git-send-email-swarren@wwwdotorg.org> <20130321065553.BC624200547@gemini.denx.de> <514B1036.3090400@ti.com> <20130321143540.B01CF200547@gemini.denx.de> Message-ID: <20130321144145.GG26945@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thu, Mar 21, 2013 at 03:35:40PM +0100, Wolfgang Denk wrote: > Dear Tom, > > In message <514B1036.3090400@ti.com> you wrote: > > > > > A system with CONFIG_SYS_HZ != 1000 is _broken_. > > > > So, RPi is going higher, and Jon hit this on I suspect omap2420h4 > > which is also higher (after mathing that all out). If we no longer > > support CONFIG_SYS_HZ != 1000 we need to make that clear (and explain > > why). > > It has never been supported, so this is not a case of "no longer". > There are several longish threads (about the timer code, especially > on ARM) in the archives. OK, then we need to do something about these platforms today. I'm guessing RPi can just be tuned down to 1000 but for omap2420h4 it's an interesting value and I don't know about the platform well enough to say what we'd need to do to adapt it. Jon? -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: